From: Keith Seitz <keiths@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] dwarf2_physname
Date: Mon, 14 Sep 2009 23:56:00 -0000 [thread overview]
Message-ID: <4AAED830.5080909@redhat.com> (raw)
In-Reply-To: <20090914224754.GA7012@caradoc.them.org>
On 09/14/2009 03:47 PM, Daniel Jacobowitz wrote:
> I'm really sorry about the rathole. I expected you'd just ask me to
> do it... you're correct that you are going to get a lot of failures
> with RealView. I have patches for some of the worst, both in
> testsuite patterns and in GDB proper. Part of the reason I haven't
> posted them yet, though, is this exact issue - one of the patches in
> our tree for RealView support is the stone-age ancestor of your
> patches :-)
>
> ICC, though, I'm pretty surprised; we get bug reports about people
> using ICC once in a while, and I thought someone had tested it...
>
> Now that you've gone to the trouble, though, let's make the most of
> your work. Could I persuade you to put the wrappers you needed and
> where to get appropriate compilers onto the GDB wiki?
Yeah, I'll work on that immediately. Of course, that means I have to
take out all the, umm, colorful language that litters my scripts. O:-)
> Ouch. Though, why does this make life difficult for the debugger?
> The problem of THIS not being artificial I've seen before - I think
> RealView has the same problem; I may have a patch to work around it -
> but I'm not sure why we care about the name of the parameter in the
> declaration.
The problem is that now we are appending the arguments to the "linkage
name" that we are computing. So when the dwarf reader sees this, it
outputs "foo::foo (foo *)" instead of "foo::foo ()". This messes up
symbol searching in some very interesting ways.
>> Is there anything else you want me to investigate?
>
> No, I'm happy. Is this patch still current? If so, I'll review it
> tonight.
Yes, the patch still applies to CVS HEAD.
Let me know if you need anything else.
Keith
next prev parent reply other threads:[~2009-09-14 23:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 22:51 Keith Seitz
2009-08-31 23:10 ` Michael Eager
2009-08-31 23:23 ` Keith Seitz
2009-08-31 23:35 ` Michael Eager
2009-09-01 22:11 ` Daniel Jacobowitz
2009-09-01 22:27 ` Daniel Jacobowitz
2009-09-01 23:18 ` Michael Eager
2009-09-01 23:37 ` Daniel Jacobowitz
2009-09-02 1:12 ` Michael Eager
2009-09-01 23:26 ` Keith Seitz
2009-09-01 23:42 ` Daniel Jacobowitz
2009-09-14 18:39 ` Keith Seitz
2009-09-14 22:48 ` Daniel Jacobowitz
2009-09-14 23:56 ` Keith Seitz [this message]
2009-09-15 13:32 ` Daniel Jacobowitz
2009-09-15 15:53 ` Keith Seitz
2009-09-15 16:12 ` Daniel Jacobowitz
2009-09-16 20:27 ` Keith Seitz
2009-09-18 22:34 ` Tom Tromey
[not found] ` <m37hwjy2tl.fsf@fleche.redhat.com>
2009-09-01 0:06 ` Michael Eager
2009-09-01 21:27 ` Tom Tromey
2009-09-01 22:10 ` Keith Seitz
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=4AAED830.5080909@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
/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