From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Cc: dberlin@dberlin.org
Subject: RFA: DW_AT_frame_base fix for complicated frames
Date: Thu, 02 Oct 2003 16:56:00 -0000 [thread overview]
Message-ID: <20031002165606.GA22819@nevyn.them.org> (raw)
Does anyone remember a specific reason why this code was there? I don't,
and I rewrote all of this stuff... I am 99.99% sure it's based on the unwind
handling for saved registers, where we get either a register number or the
address of a stack slot. But for frame bases that's not true:
A subroutine or entry point entry may also have a DW_AT_frame_base
attribute, whose value is a location description that computes the "frame
base" for the subroutine or entry point.
i.e. it computes the frame base. Not the address of the frame base. This
memory read tends to find (on x86) the return address, and then we think the
stack is at <main+34>. Oopsie.
OK? With this patch and some code Daniel Berlin and Joseph are working on,
location lists actually work. I can see all the arguments in an
-fomit-frame-pointer function from the beginning. It's really quite cool.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2003-10-02 Daniel Jacobowitz <drow@mvista.com>
* dwarf2expr.c (execute_stack_op): Don't treat the frame base as
a memory pointer.
Index: dwarf2expr.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2expr.c,v
retrieving revision 1.9
diff -u -p -r1.9 dwarf2expr.c
--- dwarf2expr.c 22 Jul 2003 15:41:59 -0000 1.9
+++ dwarf2expr.c 2 Oct 2003 16:43:21 -0000
@@ -441,18 +441,6 @@ execute_stack_op (struct dwarf_expr_cont
result = dwarf_expr_fetch (ctx, 0);
if (ctx->in_reg)
result = (ctx->read_reg) (ctx->baton, result);
- else
- {
- char *buf = alloca (TARGET_ADDR_BIT / TARGET_CHAR_BIT);
- int bytes_read;
-
- (ctx->read_mem) (ctx->baton, buf, result,
- TARGET_ADDR_BIT / TARGET_CHAR_BIT);
- result = dwarf2_read_address (buf,
- buf + (TARGET_ADDR_BIT
- / TARGET_CHAR_BIT),
- &bytes_read);
- }
result = result + offset;
ctx->stack_len = before_stack_len;
ctx->in_reg = 0;
next reply other threads:[~2003-10-02 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 16:56 Daniel Jacobowitz [this message]
2003-10-02 17:54 ` Jim Blandy
2003-10-09 14:26 ` Daniel Jacobowitz
2003-10-09 15:14 ` Andrew Cagney
2003-11-24 4:34 ` Daniel Jacobowitz
2003-11-24 16:02 ` Andrew Cagney
2003-11-24 17:03 ` 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=20031002165606.GA22819@nevyn.them.org \
--to=drow@mvista.com \
--cc=dberlin@dberlin.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