From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: "Maciej W. Rozycki" <macro@codesourcery.com>, gdb@sourceware.org
Subject: Re: MIPS: 64-bit DWARF
Date: Wed, 21 Jul 2010 22:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1007212250550.23882@digraph.polyomino.org.uk> (raw)
In-Reply-To: <m31vb4n3u6.fsf@fleche.redhat.com>
On Thu, 15 Jul 2010, Tom Tromey wrote:
> >>>>> "Maciej" == Maciej W Rozycki <macro@codesourcery.com> writes:
>
> I trimmed the CCs.
>
> Maciej> GDB as of 6.8 didn't cope at all with 64-bit DWARF records that
> Maciej> were generated for n64 binaries before the switch (for the MIPS
> Maciej> platform, that is -- I'd expect it to work for some others,
> Maciej> especially ones that have always been 64-bit like the Alpha) --
> Maciej> the usual symptom was a complete exhaustion of the stack space
> Maciej> followed by a crash (tested natively only).
>
> Could you try a newer gdb? And, if it still fails, file a bug report?
>
> gdb isn't fully ready for 64 bit DWARF (e.g., CU offsets are still just
> unsigned ints), but it shouldn't crash.
I fixed problems with GCC's 64-bit DWARF output with
<http://gcc.gnu.org/ml/gcc-patches/2006-03/msg01152.html> and switched to
32-bit output with
<http://gcc.gnu.org/ml/gcc-patches/2006-05/msg00142.html>. There won't
have been many compilers that produced correct 64-bit DWARF for this
target, rather than broken 64-bit DWARF or correct 32-bit DWARF. (And,
yes, GDB had a propensity to crash then on broken DWARF debug info, and
I'm not aware of it since having been fixed to handle broken debug info
robustly.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2010-07-21 22:54 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
2010-07-15 15:48 ` Tom Tromey
2010-07-16 14:44 ` Maciej W. Rozycki
2010-07-21 22:54 ` Joseph S. Myers [this message]
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=Pine.LNX.4.64.1007212250550.23882@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=macro@codesourcery.com \
--cc=tromey@redhat.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