From: Joel Brobecker <brobecker@adacore.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Jack Howarth <howarth@bromo.med.uc.edu>, gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 7.0 release process created
Date: Sun, 20 Sep 2009 17:12:00 -0000 [thread overview]
Message-ID: <20090920171154.GT7961@adacore.com> (raw)
In-Reply-To: <8ac60eac0909200914g39a2d471j601aebd995da1d02@mail.gmail.com>
> Ah, I see. It's true that overlapping sections are already filtered
> out, but it is not guaranteed which ones, and in fact the .text from
> a.exe is more likely to be discarded then the .text from (some) foo.o,
> because the latter will generally have lower section start.
Hmmm, I knew that it was not guaranteed that the .o sections would
be discarded, but I was hoping that it just happened to be the case.
ISTR that this was the case when I looked at the warnings that were
printed. I assumed that, after relocation, the .text section of the
.o files should always be equal or higher than the .text section of
the executable...
> Presumably you did a fair amount of testing on that.
>
> If so, should I commit that patch on the 7.0 branch (and perhaps on
> the trunk) as a temporary workaround, until Tristan comes up with a
> better fix?
That's what I suggested we do a few days ago, before we cut the branch.
But I haven't had a chance to test this much. Right now, AdaCore has
a separate branch for x86-darwin GDB, that we used to develop the port.
We're trying to move to gdb-7.0, but we haven't had time to complete
the integration and until then, testing is difficult. I definitely
plan on completing this part before 7.0 is out, however.
In the meantime, I'll see if I can reproduce Jack's issue with the
latest sources.
--
Joel
next prev parent reply other threads:[~2009-09-20 17:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 22:20 Joel Brobecker
2009-09-18 0:42 ` Tom Tromey
2009-09-18 0:49 ` Hui Zhu
2009-09-20 2:54 ` Jack Howarth
2009-09-20 3:50 ` Paul Pluzhnikov
2009-09-20 14:32 ` Joel Brobecker
2009-09-20 15:02 ` Paul Pluzhnikov
2009-09-20 15:28 ` Joel Brobecker
2009-09-20 16:14 ` Paul Pluzhnikov
2009-09-20 17:12 ` Joel Brobecker [this message]
2009-09-20 17:36 ` Jack Howarth
2009-09-20 17:40 ` Joel Brobecker
2009-09-20 18:37 ` Paul Pluzhnikov
2009-09-20 19:12 ` Jack Howarth
2009-09-20 20:22 ` Paul Pluzhnikov
2009-09-21 4:34 ` Joel Brobecker
2009-09-21 12:57 ` Jack Howarth
2009-09-21 13:36 ` Jonas Maebe
2009-09-21 13:46 ` Jack Howarth
2009-09-21 13:55 ` Jonas Maebe
2009-09-21 19:19 ` Jim Ingham
2009-09-22 12:59 ` Mark Wielaard
2009-09-22 13:30 ` Jonas Maebe
2009-09-22 14:31 ` Mark Wielaard
2009-09-22 15:56 ` Daniel Jacobowitz
2009-09-22 17:10 ` Jack Howarth
2009-09-22 17:34 ` Daniel Jacobowitz
2009-09-22 18:11 ` Mark Wielaard
2009-09-22 19:28 ` Tom Tromey
2009-09-21 13:26 ` Jack Howarth
2009-09-20 16:19 ` Paul Pluzhnikov
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=20090920171154.GT7961@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=howarth@bromo.med.uc.edu \
--cc=ppluzhnikov@google.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