Date: Wed, 11 Jun 2014 21:30:55 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Craig Rodrigues <rodrigc@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: <EA44EFB2-AF38-47FF-A48D-90744BB0244B@FreeBSD.org> In-Reply-To: <CAG=rPVf%2B6JWeGMdgfXdgnZRm6nyFQ4KbjqU-co0apgxjf-iEKg@mail.gmail.com> References: <CAG=rPVf%2B6JWeGMdgfXdgnZRm6nyFQ4KbjqU-co0apgxjf-iEKg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlOYrn0ACgkQsF6jCi4glqNUeACfQyrdsQXUv+fGLy6b6OjhSm/d lU4AoJelryqilH+pDy2GWLBckl45JJmc =c6iW -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EA44EFB2-AF38-47FF-A48D-90744BB0244B>