From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6418 invoked by alias); 30 Mar 2013 23:53:31 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 6383 invoked by uid 89); 30 Mar 2013 23:53:24 -0000 X-Spam-SWARE-Status: No, score=-9.6 required=5.0 tests=AWL,BAYES_00,KHOP_PGP_SIGNED,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,TW_BJ,TW_JC autolearn=ham version=3.3.1 Received: from smtp.gentoo.org (HELO smtp.gentoo.org) (140.211.166.183) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sat, 30 Mar 2013 23:53:21 +0000 Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 61DE633D8CC; Sat, 30 Mar 2013 23:53:19 +0000 (UTC) From: Mike Frysinger To: gdb@sourceware.org Subject: Re: Backtraces broken on i386 by unorthodox encoding of push %ebp Date: Sat, 30 Mar 2013 23:53:00 -0000 User-Agent: KMail/1.13.7 (Linux/3.7.6; KDE/4.6.5; x86_64; ; ) Cc: Richard Smith , Jan Kratochvil References: <20130330195008.GA11994@host2.jankratochvil.net> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1446460.aApvKWQU3x"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201303301958.20619.vapier@gentoo.org> X-Virus-Found: No X-SW-Source: 2013-03/txt/msg00088.txt.bz2 --nextPart1446460.aApvKWQU3x Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-length: 1516 On Saturday 30 March 2013 17:02:55 Richard Smith wrote: > Jan Kratochvil wrote: > > You should always provide unwind information and then it is irrelevant > > which instructions and/or which their coding you use. >=20 > Yes, you're right, I could quite easily. But a design > criterion for this project is that it is easy for > third-parties to produce backtraces from production code > (i.e. once debugging information has been stripped). do what all the distros are doing now: split the debug files out into dedic= ated=20 files. then wherever you run gdb, d/l the debug files first and point gdb = at=20 them. objcopy --only-keep-debug file file.debug strip file > Joel Brobecker wrote: > > But if he cannot get the unwind information with the > > binary, it might indeed be easy enough to improve the > > prologue analyzer for x86. On x86_64, on the other hand, > > we made the conscious design decision to rely more on > > unwind info, so it's a little more questionable whether > > we'd want to do that for this target. > >=20 > > The thing I wanted to add to Richard is that there is a > > very high chance that the only way to get this fixed in > > GDB is by submitting a patch himself (to gdb-patches). >=20 > I'll certainly take a look at it to see if it's as > straightforward as it seems. >=20 > However, I expect the same problem will arise on x86_64, and > I can understand not wanting to complicate unnecessarily its > prologue analyzer. i think all the sniffers live in gdb/i386-tdep.c -mike --nextPart1446460.aApvKWQU3x Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. Content-length: 836 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAABAgAGBQJRV3wcAAoJEEFjO5/oN/WBFhgP/220l1LV6B5GoqNYKH9Nigqr wEPYmkyS8KqUB7/jFCL2s9DCO7GVFUpSkFNjY21TofAZSehREgoSBY63EsCjuUdw zjmN45wjJ4ftOZQBh+osq7fqEQDCEsJ+dxHIuwTkOh2ITGF+9Wx6IN+w22FE1AF3 2T77YVE4oBepW2oz7rhBiAr9iE3JoV0tPpfsZaeTl31fMLr1hSts0g11ze2Mus/W BpeKPJLULlXxlwp4UMtH8X0C0QFFxXeel8AiKF0+5R49FjAtt88lxD5u14fjnpgN lQC05EvY7K5jwWJsOFTgCHBJQ1RGfhBafHe/fsguPFRpx/3rKpitRNPOPufnFeNl ymP+/kxdfaAEtsuxZLfRKEICb7g8NGSNiisLDkP9jFRLt0Y5JRM9z+dV4MvUdcoB cvLWyTcdAjJq2eavrM0ID+muDAUYB3r+oCznArpOdj9HpnnS6xDyXz1cu3b3nSOz 174/GHyfgFWyqAx9CTz91TW6qeQmgEfkEPH9gA73gy2v4Hqxf1l04EfrFtBdUWxm OIBlRNdbqtkm2TBk7ZfRd7djCRn2HGyTJ3wsEhgRgtDJ9P+LfyZoizOxHrg6tkPA PyLS1yieYhDw3289JiAOBjkbGmzWjopVutzNfHzATGEsggfb2fNgTc8ozeafiQJU NNc+rY2spvMN7GR8KNhU =hHvu -----END PGP SIGNATURE----- --nextPart1446460.aApvKWQU3x--