From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
binutils@sourceware.org,
Jan Kratochvil <jan.kratochvil@redhat.com>,
Andrew Stubbs <ams@codesourcery.com>,
gdb@sourceware.org, Nathan Sidwell <nathan@codesourcery.com>
Subject: Re: MIPS: 64-bit DWARF
Date: Wed, 14 Jul 2010 18:44:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1007141926271.29495@tp.orcam.me.uk> (raw)
In-Reply-To: <4C3DEC14.8090601@caviumnetworks.com>
On Wed, 14 Jul 2010, David Daney wrote:
> > Here is the patch that I tested for (a non-HEAD version of) binutils.
> > This makes prelink happy, and there are no regressions in the GDB
> > testsuite. (Anything else to test?) I left in the 64-bit stuff for
> > TE_IRIX, as I have no idea about it.
>
> How was it tested? Have you tested mips64-linux-gnu with -mabi=64?
GCC switched to emitting 32-bit DWARF records on the MIPS/Linux/n64
platform a couple of years ago. GDB as of 6.8 didn't cope at all with
64-bit DWARF records that were generated for n64 binaries before the
switch (for the MIPS platform, that is -- I'd expect it to work for some
others, especially ones that have always been 64-bit like the Alpha) --
the usual symptom was a complete exhaustion of the stack space followed by
a crash (tested natively only). I am strongly convinced GAS should
follow, for consistency if nothing else, and I am rather surprised both
tools were not updated at once.
TE_IRIX refers to the original 64-bit DWARF stuff invented by SGI that
predates DWARF-3 and differs slightly from the latter. This may perhaps
be the reason of the GDB crash -- it may have this SGI variant hardcoded
for the MIPS target or suchlike. Having noticed the GCC switch I have not
investigated it further.
The change needs to be properly tested of course to see if it does not
uncover an odd bug somewhere, but in principle I consider it the right and
necessary move.
Maciej
next prev parent reply other threads:[~2010-07-14 18:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 12:48 debug problem with prelinked libraries Andrew Stubbs
2010-05-05 14:35 ` Daniel Jacobowitz
2010-05-05 14:59 ` Andrew Stubbs
2010-05-07 13:23 ` Jan Kratochvil
2010-05-07 13:26 ` Andrew Stubbs
2010-07-01 15:43 ` Thomas Schwinge
2010-07-06 9:59 ` MIPS: 64-bit DWARF (was: debug problem with prelinked libraries) Thomas Schwinge
2010-07-14 8:50 ` MIPS: 64-bit DWARF Thomas Schwinge
2010-07-14 16:56 ` David Daney
2010-07-14 18:44 ` Maciej W. Rozycki [this message]
2010-07-15 15:48 ` Tom Tromey
2010-07-16 14:44 ` Maciej W. Rozycki
2010-07-21 22:54 ` Joseph S. Myers
2010-07-22 5:28 ` Tom Tromey
2010-07-16 11:22 ` Thomas Schwinge
2010-07-19 20:00 ` Richard Sandiford
2010-07-22 7:41 ` Thomas Schwinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.10.1007141926271.29495@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=ams@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=ddaney@caviumnetworks.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=nathan@codesourcery.com \
--cc=thomas@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox