From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@mvista.com, ian@wasabisystems.com
Cc: gdb@sources.redhat.com
Subject: Re: C++/Java regressions
Date: Wed, 26 Nov 2003 21:18:00 -0000 [thread overview]
Message-ID: <20031126211736.D4E7F4B40B@berman.michael-chastain.com> (raw)
ian> Good question. My guess is that it's because lookup_symbol_aux()
ian> calls current_language->la_lookup_symbol_nonlocal() before it calls
ian> lookup_symbol_aux_psymtabs(). If I force la_lookup_symbol_nonlocal()
ian> to return NULL, then lookup_symbol_aux_psymtabs() finds the typedef,
ian> and `ptype T5<int>' works more or less correctly.
Have a look at
http://sources.redhat.com/gdb/bugs/1465
I just mailed in an analysis of a similar bug. It will take some
time for gnats to post it.
Briefly, the call tree is:
lookup_symbol_aux
current_language->la_lookup_symbol_nonlocal
lookup_symbol_file
lookup_symbol_static [1]
lookup_symbol_aux_block
lookup_symbol_global [2]
lookup_possible_namespace_symbol [3]
lookup_symbol_aux_symtabs [4]
lookup_symbol_aux_psymtabs
You are probably getting a hit at [3].
Check the value of "block" in lookup_symbol_file. I bet that
you have block=0. That prevents [1] from finding a match in the current
static block.
[4] is a kludge that looks in ALL static blocks. That's not good.
Before [3] came along as part of DavidC's namespace work,
[4] was happening all the time.
I think the right fix is to pass a correct "block" to local_symbol_aux
so that [1] can do its job properly.
Michael C
next reply other threads:[~2003-11-26 21:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 21:18 Michael Elizabeth Chastain [this message]
2003-11-26 21:33 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2003-11-26 22:48 Michael Elizabeth Chastain
2003-11-26 21:44 Michael Elizabeth Chastain
2003-11-26 22:21 ` Ian Lance Taylor
2003-11-26 22:28 ` Daniel Jacobowitz
2003-11-26 22:34 ` Ian Lance Taylor
2003-11-25 17:06 Michael Elizabeth Chastain
2003-11-25 17:14 ` David Carlton
2003-11-25 17:59 ` Daniel Jacobowitz
2003-11-25 15:33 Michael Elizabeth Chastain
2003-11-25 14:49 Michael Elizabeth Chastain
2003-11-25 15:06 ` Daniel Jacobowitz
2003-11-25 4:44 Michael Elizabeth Chastain
2003-11-25 17:54 ` Ian Lance Taylor
2003-11-25 1:37 David Carlton
2003-11-25 3:58 ` Ian Lance Taylor
2003-11-26 4:04 ` Ian Lance Taylor
2003-11-26 15:32 ` Daniel Jacobowitz
2003-11-26 21:05 ` Ian Lance Taylor
2003-11-26 21:11 ` David Carlton
2003-11-26 21:12 ` Daniel Jacobowitz
2003-11-26 21:32 ` Ian Lance Taylor
2003-12-01 16:45 ` Daniel Jacobowitz
2003-11-30 2:57 ` Jim Blandy
2003-11-30 3:12 ` Daniel Jacobowitz
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=20031126211736.D4E7F4B40B@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=ian@wasabisystems.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