Date: Wed, 11 Jun 2014 22:39:49 +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: <11764709-BB10-47C5-B537-5AC5A0A0E2E6@FreeBSD.org> In-Reply-To: <CAG=rPVeBojBM7MyE=0ropwWUODxs6_G4z6RXYpkypnmUDf2rtQ@mail.gmail.com> References: <CAG=rPVf%2B6JWeGMdgfXdgnZRm6nyFQ4KbjqU-co0apgxjf-iEKg@mail.gmail.com> <EA44EFB2-AF38-47FF-A48D-90744BB0244B@FreeBSD.org> <CAG=rPVeBojBM7MyE=0ropwWUODxs6_G4z6RXYpkypnmUDf2rtQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_B9FB59A4-79B1-4144-ACE0-291B0AFCB25A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 11 Jun 2014, at 21:56, Craig Rodrigues <rodrigc@FreeBSD.org> wrote: > 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: >>>=20 >>> 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: >>>=20 >>> = http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-June/002606= .html >>=20 >> Can you please post the output of the following? >>=20 >> objdump -W /usr/local/sbin/libvirtd | head >>=20 >> -Dimitry >>=20 >=20 > $ objdump -W /usr/local/sbin/libvirtd | head >=20 > /usr/local/sbin/libvirtd: file format elf64-x86-64-freebsd >=20 > The section .debug_aranges contains: >=20 > Length: 92 > Version: 2 > Offset into .debug_info: 0 > Pointer Size: 8 > Segment Size: 0 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. Can you post the complete objdump output instead, or post just the part under "The section .debug_info contains"? That should look similar to: The section .debug_info contains: Compilation Unit @ offset 0x0: Length: 59 Version: 4 Abbrev Offset: 0 Pointer Size: 4 [...] but with possibly another "Version:" line. -Dimitry --Apple-Mail=_B9FB59A4-79B1-4144-ACE0-291B0AFCB25A Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlOYvqEACgkQsF6jCi4glqPEAACg9iqYRyH9cjMBDhAw/1/3ZI8F OZkAoJVMjiuem2mQ9N8ySy5KGd30Z9Qh =kX7z -----END PGP SIGNATURE----- --Apple-Mail=_B9FB59A4-79B1-4144-ACE0-291B0AFCB25A--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11764709-BB10-47C5-B537-5AC5A0A0E2E6>