Date: Wed, 11 Jun 2014 12:56:27 -0700 From: Craig Rodrigues <rodrigc@FreeBSD.org> To: Dimitry Andric <dim@freebsd.org> Cc: Glen Barber <gjb@freebsd.org>, freebsd-toolchain@freebsd.org, freebsd-arch <freebsd-arch@freebsd.org> Subject: Re: gdb in CURRENT cannot debug userland cores, when is kernel lldb coming? Message-ID: <CAG=rPVeBojBM7MyE=0ropwWUODxs6_G4z6RXYpkypnmUDf2rtQ@mail.gmail.com> In-Reply-To: <EA44EFB2-AF38-47FF-A48D-90744BB0244B@FreeBSD.org> References: <CAG=rPVf%2B6JWeGMdgfXdgnZRm6nyFQ4KbjqU-co0apgxjf-iEKg@mail.gmail.com> <EA44EFB2-AF38-47FF-A48D-90744BB0244B@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 11, 2014 at 12:30 PM, Dimitry Andric <dim@freebsd.org> wrote: > On 11 Jun 2014, at 20:53, Craig Rodrigues <rodrigc@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: >> >> http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-June/002606.html > > Can you please post the output of the following? > > objdump -W /usr/local/sbin/libvirtd | head > > -Dimitry > $ objdump -W /usr/local/sbin/libvirtd | head /usr/local/sbin/libvirtd: file format elf64-x86-64-freebsd The section .debug_aranges contains: Length: 92 Version: 2 Offset into .debug_info: 0 Pointer Size: 8 Segment Size: 0 -- Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVeBojBM7MyE=0ropwWUODxs6_G4z6RXYpkypnmUDf2rtQ>