Results 1 to 9 of 9

Thread: FreeBSD 10.0 Alpha 4 Plays With LLDB, Xen PVHVM

  1. #1
    Join Date
    Jan 2007
    Posts
    15,131

    Default FreeBSD 10.0 Alpha 4 Plays With LLDB, Xen PVHVM

    Phoronix: FreeBSD 10.0 Alpha 4 Plays With LLDB, Xen PVHVM

    While we're still awaiting the release of FreeBSD 9.2, FreeBSD 10.0 is now up to its fourth alpha release...

    http://www.phoronix.com/vr.php?view=MTQ3MzM

  2. #2
    Join Date
    Dec 2011
    Posts
    2,107

    Default lldb

    What does it mean to connect LLDB to the build?

    I don't understand.

    Could this be done for Linux too?

  3. #3
    Join Date
    Jan 2013
    Posts
    1,116

    Default

    Quote Originally Posted by tron_ston View Post
    lldb is horrible, it should be replaced with gdb
    And I am sure you have the knowledge that is needed to come to such a conclusion. So maybe instead of putting a blank statement here tell us your reasons to come to that conclusion?

  4. #4
    Join Date
    Oct 2012
    Location
    Washington State
    Posts
    486

    Default

    Quote Originally Posted by tron_ston View Post
    lldb is horrible, it should be replaced with gdb
    Keep talking out your back side. It's rather vast and vacuous.

  5. #5
    Join Date
    Oct 2012
    Location
    Washington State
    Posts
    486

    Default LIBC++ for Linux now turned on

    On a plus side,

    LLVM/Clang/Clang-Tools-Extra/LLDB/Compiler-RT/Libc++ under the /projects directory finally builds Clang with Libc++ by default.

    Now that both libc++abi and libc++ are feature complete [sans full Generic Lambda support] I expect Intel's OpenMP expansion and the many SoC projects to start folding into trunk very soon.

    Nice to finally get Libc++ building properly.

    Debian:

    CC=clang (clang-3.3) CXX=clang++ (clang++-3.3) cmake ../llvm with all available subprojects


    /llvm
    /llvm/projects
    /llvm/projects/compiler-rt
    /llvm/projects/libcxx
    /llvm/projects/test-suite
    /llvm/tools
    /llvm/tools/clang
    /llvm/tools/clang/tools/extra
    /llvm/tools/lldb

    All builds cleanly with Cmake.

    The Documentation project is getting a lot of clean up, as well. Tutorials and more to make learning the projects are also a priority.

  6. #6
    Join Date
    Oct 2010
    Posts
    92

    Default

    Quote Originally Posted by uid313 View Post
    What does it mean to connect LLDB to the build?

    I don't understand.

    Could this be done for Linux too?
    Technically, it just means "it will be compiled by default when building the base system". Linux is a bit different, in that there isn't really a base system ... it's vaguely like if debian decided to include it in build-essentials.

  7. #7
    Join Date
    Oct 2010
    Posts
    92

    Default

    Quote Originally Posted by dnebdal View Post
    Technically, it just means "it will be compiled by default when building the base system". Linux is a bit different, in that there isn't really a base system ... it's vaguely like if debian decided to include it in build-essentials.
    Looking at it: Not even that, it means "it's in the base system source and there is infrastructure to build and install it". It defaults to not being built, for now.

    Also, the epoll support isn't in this alpha, it apparently has some issues.

  8. #8
    Join Date
    Dec 2011
    Posts
    2,107

    Default

    Quote Originally Posted by dnebdal View Post
    Technically, it just means "it will be compiled by default when building the base system". Linux is a bit different, in that there isn't really a base system ... it's vaguely like if debian decided to include it in build-essentials.
    Ah, I see. Thanks for the clarification!
    Now I understand!

    I thought it did establish a connection (over some socket or bus) for debugging the kernel, or something, or integrated the debugger with the kernel somehow.

  9. #9
    Join Date
    Feb 2012
    Posts
    253

    Default

    I'd like to five lldb a try; over the time, I've found gdb not to have the stability I'd expect from a debugger. Not only have I had seg. faults in the middle of a debug, but I've also seen strange behaviour, specially debugging multithreaded programs. This is not to say that gdb hasn't been very useful to me, of course.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •