From owner-freebsd-toolchain@FreeBSD.ORG Wed Jun 11 20:40:07 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 397865B1; Wed, 11 Jun 2014 20:40:07 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E6028237C; Wed, 11 Jun 2014 20:40:06 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::c5cc:f189:593d:8554] (unknown [IPv6:2001:7b8:3a7:0:c5cc:f189:593d:8554]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 398F05C37; Wed, 11 Jun 2014 22:40:03 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_B9FB59A4-79B1-4144-ACE0-291B0AFCB25A"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: gdb in CURRENT cannot debug userland cores, when is kernel lldb coming? From: Dimitry Andric In-Reply-To: Date: Wed, 11 Jun 2014 22:39:49 +0200 Message-Id: <11764709-BB10-47C5-B537-5AC5A0A0E2E6@FreeBSD.org> References: To: Craig Rodrigues X-Mailer: Apple Mail (2.1878.2) Cc: Glen Barber , freebsd-toolchain@freebsd.org, freebsd-arch X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2014 20:40:07 -0000 --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 wrote: > On Wed, Jun 11, 2014 at 12:30 PM, Dimitry Andric = wrote: >> On 11 Jun 2014, at 20:53, Craig Rodrigues = 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--