From: Tristan Gingold <gingold@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFA/DWARF] Do not load .eh_frame section from separete object files
Date: Sat, 02 Jul 2011 11:09:00 -0000 [thread overview]
Message-ID: <6B66CB2F-05FA-4620-902F-33EE89D0ECB3@adacore.com> (raw)
In-Reply-To: <m3k4c194ja.fsf@fleche.redhat.com>
On Jul 1, 2011, at 9:36 PM, Tom Tromey wrote:
>>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>
> Joel> We don't need to read the .eh_frame section from the separate
> Joel> object files, because this data is already present in the
> Joel> main executable (it needs to, or the program wouldn't work).
>
> In the .debug files I looked at, the .eh_frame section is marked NOBITS.
> I wonder why this isn't the case for you.
That's not the case on Darwin, as separate files are object files in this case.
> Joel> Tested on x86_64-linux as well as x86_64-darwin. OK to commit?
>
> The patch itself seems fine to me.
>
> Tom
next prev parent reply other threads:[~2011-07-02 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 18:01 Joel Brobecker
2011-07-01 19:37 ` Tom Tromey
2011-07-02 11:09 ` Tristan Gingold [this message]
2011-07-04 16:43 ` Joel Brobecker
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=6B66CB2F-05FA-4620-902F-33EE89D0ECB3@adacore.com \
--to=gingold@adacore.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--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