From: Josef Zlomek <zlomj9am@artax.karlin.mff.cuni.cz>
To: Richard Henderson <rth@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Problem with location lists and variables on stack
Date: Mon, 06 Oct 2003 06:40:00 -0000 [thread overview]
Message-ID: <20031006064016.GA13046@artax.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20031006062216.GB26462@redhat.com>
> > No, but DW_AT_frame_base should be a location list describing the
> > changes in the frame base.
>
> How can we just describe "please use the CFA" and avoid duplicating
> this part of the unwind info?
Daniel Berlin has already written support for GCC to generate location
list for DW_AT_frame_base.
DW_AT_frame_base is a location list as any other (actually only the
offsets relatively to original stack pointer at function start are needed).
GDB then uses this location list to adjust offsets of other variables
addressed using stack pointer.
With Daniel Jacobowitz's fix for GDB it works :-)
i.e. you can see correct values for variables located on stack
even when stack pointer changes because of push, pop, etc.
Current GCC patch can be downloaded from:
http://artax.karlin.mff.cuni.cz/~zlomj9am/download/vt-main.patch
(because currently GCC is in stage 2 it has to wait until GCC is in stage 1)
Josef
next prev parent reply other threads:[~2003-10-06 6:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 14:43 Josef Zlomek
2003-10-01 14:49 ` Daniel Jacobowitz
2003-10-01 15:21 ` Josef Zlomek
2003-10-01 15:44 ` Josef Zlomek
2003-10-01 15:54 ` Daniel Jacobowitz
2003-10-01 16:03 ` Josef Zlomek
2003-10-01 16:22 ` Daniel Jacobowitz
2003-10-01 17:41 ` Josef Zlomek
2003-10-01 17:44 ` Daniel Jacobowitz
2003-10-01 17:48 ` Josef Zlomek
2003-10-06 6:22 ` Richard Henderson
2003-10-06 6:40 ` Josef Zlomek [this message]
2003-10-06 13:46 ` Daniel Jacobowitz
2003-10-06 14:49 ` Daniel Berlin
2003-10-07 21:48 ` Daniel Jacobowitz
2003-10-08 5:09 ` Josef Zlomek
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=20031006064016.GA13046@artax.karlin.mff.cuni.cz \
--to=zlomj9am@artax.karlin.mff.cuni.cz \
--cc=gdb@sources.redhat.com \
--cc=rth@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