From: Tom Tromey <tromey@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: "Maciej W. Rozycki" <macro@codesourcery.com>, gdb@sourceware.org
Subject: Re: MIPS: 64-bit DWARF
Date: Thu, 22 Jul 2010 05:28:00 -0000 [thread overview]
Message-ID: <m3k4oo6q6m.fsf@fleche.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1007212250550.23882@digraph.polyomino.org.uk> (Joseph S. Myers's message of "Wed, 21 Jul 2010 22:54:11 +0000 (UTC)")
>>>>> "Joseph" == Joseph S Myers <joseph@codesourcery.com> writes:
Joseph> (And, yes, GDB had a propensity to crash then on broken DWARF
Joseph> debug info, and I'm not aware of it since having been fixed to
Joseph> handle broken debug info robustly.)
There have been a couple of robustness fixes in recent times, but not
for anything that might have caused a crash.
For future reference, I'm happy to fix this sort of problem, but I would
need a test case. An object file of whatever form should be fine.
I'd imagine these bugs go unfound just because it is unusual to come
across DWARF that is bad in just the right way.
Tom
next prev parent reply other threads:[~2010-07-22 5:28 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
2010-07-22 5:28 ` Tom Tromey [this message]
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=m3k4oo6q6m.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=macro@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).