From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro_alves@portugalmail.pt>, gdb-patches@sourceware.org
Subject: Re: [win32] wrong solib from/to addresses
Date: Wed, 13 Jun 2007 09:31:00 -0000 [thread overview]
Message-ID: <20070613093313.GA6426@adacore.com> (raw)
In-Reply-To: <20070613022150.GA12337@ednor.casa1.cgf.cx>
> > I had a similar patch here, that I dumped in favor of a rewrite
> > of win32 solibs on top of Daniel's pending solib-target.c.
>
> That sounds like the right way to go to me. Can we hold of on this
> until Daniel's changes are in?
As far as I'm concerned, I'm happy to withdraw this patch. I don't
think that the consequences of these wrong addresses are that bad,
so there is certainly no huge hurry.
At the AdaCore level, we have a tiny local change in the x86 unwinder
where we decided to take a different choice than Mark did, and that
choice involves a heuristic that needs to determine whether we're
in a DLL or not. So this patch is a bit more urgent for us, but we
have it installed in our local tree, so we're good to go.
As far as the FSF tree is concerned, apart from the fact that
the addresses are wrong when the users asks for that information,
the only other visible symptom is a minor error in the backtrace.
For frames that involve a DLL symbol, the name of the DLL where
this symbol comes from can be either printed wrong, or not printed
at all. I had never noticed this until I hit this issue with our
local patch when testing on Vista.
So patch withdrawn for now, and the puck moves to Daniel and Pedro.
--
Joel
prev parent reply other threads:[~2007-06-13 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 20:47 Joel Brobecker
2007-06-12 23:33 ` Pedro Alves
2007-06-13 2:21 ` Christopher Faylor
2007-06-13 3:09 ` Daniel Jacobowitz
2007-06-13 3:14 ` Christopher Faylor
2007-06-13 9:39 ` Joel Brobecker
2007-06-13 11:17 ` Daniel Jacobowitz
2007-06-13 9:31 ` Joel Brobecker [this message]
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=20070613093313.GA6426@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/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