From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
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: Mon, 08 Nov 2004 00:19:00 -0000 [thread overview]
Message-ID: <20041107171557.GA9121@nevyn.them.org> (raw)
In-Reply-To: <200411071628.iA7GSfwL022610@elgar.sibelius.xs4all.nl>
On Sun, Nov 07, 2004 at 05:28:41PM +0100, Mark Kettenis wrote:
> 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.
Ah! I understand now, thanks.
I think GDB should complain noisily about this. One nice fix to this
in gas would be for it to detect the format of .debug_info and match it
when generating .debug_line. Another would be to add command line
options for 32-bit and 64-bit .debug_line and make GCC instruct it on
which to use - that's a bit more complicated to implement.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-11-07 17:16 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
2004-11-08 0:19 ` Daniel Jacobowitz [this message]
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=20041107171557.GA9121@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=echristo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
--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).