From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: [obish/dwarf2] Describe frame-base hack
Date: Mon, 26 Jan 2004 19:57:00 -0000 [thread overview]
Message-ID: <4015711E.6090005@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 126 bytes --]
Hello,
Stumbled across this during testing of symbol_ops. This adds a comment
alerting the reader as to a problem.
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1195 bytes --]
Index: ChangeLog
2004-01-26 Andrew Cagney <cagney@redhat.com>
* dwarf2read.c (read_func_scope): Document hack.
Index: dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.124
diff -u -r1.124 dwarf2read.c
--- dwarf2read.c 23 Jan 2004 22:41:28 -0000 1.124
+++ dwarf2read.c 26 Jan 2004 19:54:06 -0000
@@ -2211,6 +2211,15 @@
it. */
attr = dwarf_attr (die, DW_AT_frame_base);
if (attr)
+ /* FIXME: cagney/2004-01-26: The DW_AT_frame_base's location
+ expression is being recorded directly in the function's symbol
+ and not in a separate frame-base object. I guess this hack is
+ to avoid adding some sort of frame-base adjunct/annex to the
+ function's symbol :-(. The problem with doing this is that it
+ results in a function symbol with a location expression that
+ has nothing to do with the location of the function, ouch! The
+ relationship should be: a function's symbol has-a frame base; a
+ frame-base has-a location expression. */
dwarf2_symbol_mark_computed (attr, new->name, cu);
list_in_scope = &local_symbols;
next reply other threads:[~2004-01-26 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 19:57 Andrew Cagney [this message]
2004-01-26 20:42 ` 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=4015711E.6090005@gnu.org \
--to=cagney@gnu.org \
--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