From: "Paul N. Hilfinger" <hilfingr@otisco.mckusick.com>
To: carlton@kealia.com
Cc: gdb-patches@sources.redhat.com
Subject: Interactions of symbol-lookup with language
Date: Sat, 08 Nov 2003 22:55:00 -0000 [thread overview]
Message-ID: <200311082255.hA8MtJK08216@otisco.McKusick.COM> (raw)
David,
The symbol-lookup facilities are now organized to adapt themselves to
the current language. We've encountered some problems with this.
In particular, in decode_line_1, there is a call to find_imps, an
Objective C function, which in turn calls lookup_symbol. When
decode_line_1 is called while in Ada mode, this latter lookup_symbol
acts like an Ada symbol lookup, which makes little sense given that
find_imps is concerned with Objective C code. We have encountered
cases where the result is anomalous.
Our fix for the moment is simply to put a wrapper around decode_objc
to force the language to objc temporarily. We are a little
uncomfortable with submitting this kind of kludge publicly, and
would prefer something officially blessed. One possibility is to have
a variant of lookup_symbol that allows one to specify a prevailing
language for those cases where it matters. We have at least one other
place where we'd like to "look up a symbol as in C".
In any case, we'd welcome your (and other maintainers') comments.
Paul Hilfinger
ACT, Inc.
next reply other threads:[~2003-11-08 22:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-08 22:55 Paul N. Hilfinger [this message]
2003-11-10 17:07 ` David Carlton
2004-01-20 10:16 ` [RFC] Proposed changes in symbol-handling for Ada Paul Hilfinger
2004-01-20 15:01 ` Daniel Jacobowitz
2004-01-21 10:55 ` Paul Hilfinger
2004-01-21 15:19 ` Daniel Jacobowitz
2004-01-23 21:08 ` Andrew Cagney
2004-01-20 23:05 ` David Carlton
2004-01-21 11:22 ` Paul Hilfinger
2004-01-21 16:49 ` David Carlton
2004-01-21 18:50 ` Daniel Jacobowitz
2003-11-11 1:23 ` Interactions of symbol-lookup with language Elena Zannoni
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=200311082255.hA8MtJK08216@otisco.McKusick.COM \
--to=hilfingr@otisco.mckusick.com \
--cc=Hilfinger@gnat.com \
--cc=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.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