Ed,
Can we enable WITH_LLDB=yes by default in
CURRENT only? It took me a while to figure out that I needed
to build/install lldb to debug some of my coredumps in CURRENT.
I realize that things are in motion with respect to the toolchain,
but it is annoying that in CURRENT, we have a debugger in
Hi,
Recently when trying to debug some coredumps in CURRENT from
a userland process in the devel/libvirt port, I found that the gdb in
base could not get a backtrace from the core file:
http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-June/002606.html
I needed to add to my
On 11 June 2014 14:53, Craig Rodrigues rodr...@freebsd.org wrote:
Is anyone working on a kernel lldb? When is it expected to be ready?
Kernel LLDB support is an ongoing Summer of Code project this year.
I'm not sure it's feasible for 10.1 though.
___
On 11 Jun 2014, at 20:53, Craig Rodrigues rodr...@freebsd.org wrote:
Recently when trying to debug some coredumps in CURRENT from
a userland process in the devel/libvirt port, I found that the gdb in
base could not get a backtrace from the core file:
On Wed, Jun 11, 2014 at 12:34 PM, Warner Losh i...@bsdimp.com wrote:
Except for kgdb functionality, the gdb ports (both the 6.x and 7.x ones) work
much better than the gdb in the tree. This may be a good stop-gap until lldb
is ready.
Warner
I installed devel/gdb which installs gdb762.
On 11 Jun 2014, at 21:56, Craig Rodrigues rodr...@freebsd.org wrote:
On Wed, Jun 11, 2014 at 12:30 PM, Dimitry Andric d...@freebsd.org wrote:
On 11 Jun 2014, at 20:53, Craig Rodrigues rodr...@freebsd.org wrote:
Recently when trying to debug some coredumps in CURRENT from
a userland process
On Wed, Jun 11, 2014 at 1:39 PM, Dimitry Andric d...@freebsd.org wrote:
Ah sorry, your objdump prints sections in a different order than mine.
I was mainly interested in the DWARF version of debug information; maybe
the way you built libvirt has caused it to contain DWARF4 instead of
DWARF2.
