From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gcc@gcc.gnu.org, binutils@sources.redhat.com,
echristo@redhat.com, seufer@csv.ica.uni-stuttgart.de,
gdb@sources.redhat.com
Subject: Re: Mixing 32-bit and 64-bit DWARF2/3 sections
Date: Sun, 07 Nov 2004 17:16:00 -0000 [thread overview]
Message-ID: <200411071628.iA7GSfwL022610@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20041107153144.GA7039@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 7 Nov 2004 10:31:44 -0500)
Date: Sun, 7 Nov 2004 10:31:44 -0500
From: Daniel Jacobowitz <drow@false.org>
On Sun, Nov 07, 2004 at 03:28:07PM +0100, Mark Kettenis wrote:
> Currently GDB barfs when you use it on an executable that contains
> compilation units that mix 32-bit and 64-bit DWARF sections. Looking
> at the (latest?) DWARF3 draft it doesn't seem to be unreasonable that
> it does so:
>
> "The 32-bit and 64-bit DWARF format conventions must not be
> intermixed within a single compilation unit."
I'd read that as saying that GDB should support what you describe.
This isn't mixing them within a single compilation unit. What falls
down?
No I'm really talking about mixing 32-bit and 64-bit DWARF format
within the same compilation unit. In the case of OpenBSD/mips64 GCC
generates a 32-bit .debug_info section and .file directives that
contain the line info. These .file directives are then converted by
gas into 64-bit .debug_line sections.
When GDB reads these it dumps core. I'm working on patches to fix
this, but I'm not yet completely satisfied with them.
Mark
next prev parent reply other threads:[~2004-11-07 16:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 15:31 Mark Kettenis
2004-11-07 16:29 ` Daniel Jacobowitz
2004-11-07 17:16 ` Mark Kettenis [this message]
2004-11-08 0:19 ` Daniel Jacobowitz
2004-11-08 21:44 ` James E Wilson
2004-11-08 23:03 ` Mark Kettenis
2004-11-08 23:37 ` James E Wilson
2004-11-08 23:46 ` Thiemo Seufer
2004-11-08 23:55 ` Daniel Berlin
2004-11-09 0:15 ` James E Wilson
2004-11-08 23:50 ` Daniel Jacobowitz
2004-11-09 0:29 ` James E Wilson
2004-11-09 20:58 ` Dean Luick
2004-11-09 22:10 David Anderson
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=200411071628.iA7GSfwL022610@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=binutils@sources.redhat.com \
--cc=drow@false.org \
--cc=echristo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=seufer@csv.ica.uni-stuttgart.de \
/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).