From: Keith Seitz <keiths@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Revisit PR 16253 ("Attempt to use a type name...")
Date: Thu, 25 Jun 2015 18:26:00 -0000 [thread overview]
Message-ID: <558C47DE.2070602@redhat.com> (raw)
In-Reply-To: <047d7b2e4e86d2189d05194b7fc3@google.com>
On 06/24/2015 04:02 PM, Doug Evans wrote:
> A variation of PR 18150?
> You need to put the symbols in an unexpanded symtab,
> the catch being that gdb expands the symtab with main() at startup.
>
Doh! That does indeed do it!
> > Nonetheless it is not quite so straight-forward in the BLOCK_FUNCTION
> > case where we have to decide what is a "better" match:
> >
> > SYMBOL_DOMAIN == domain && SYMBOL_IS_ARGUMENT
> >
> > or
> > SYMBOL_DOMAIN != domain (but symbol_matches_domain returns 1) &&
> > !SYMBOL_IS_ARGUMENT
>
> I'm not sure either. I'm not sure the BLOCK_FUNCTION case
> can even exercise this bug.
Forest/trees. Darn my vision! :-)
>
> > In that case, I cannot say which is more correct. Moreover I have been
> > unable to figure out how to test this. I worry that I would simply be
> > introducing a regression. IMO this is getting into "risky" territory.
> > [But then my philosophy is "if it ain't broke, don't fix it." As far as
> > I can tell, block_lookup_symbol is not "broke."]
> >
> > So what do maintainers want me to do?
>
> How about this?
That looks good to me, and is fully covered by the test suite.
/me very happy
Keith
next prev parent reply other threads:[~2015-06-25 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 23:02 Doug Evans
2015-06-25 18:26 ` Keith Seitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-24 16:54 Doug Evans
2015-06-16 17:54 Doug Evans
2015-06-16 21:02 ` Doug Evans
2015-06-17 15:46 ` Keith Seitz
2015-06-11 18:57 Keith Seitz
2015-06-16 16:29 ` Jan Kratochvil
2015-06-17 12:34 ` Jan Kratochvil
2015-06-17 15:50 ` Keith Seitz
2015-06-23 18:39 ` Keith Seitz
2015-06-23 19:53 ` Jan Kratochvil
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=558C47DE.2070602@redhat.com \
--to=keiths@redhat.com \
--cc=dje@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).