From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: jimb@codesourcery.com (Jim Blandy)
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: tracepoints: abstract frame base finding in dwarf2loc.c
Date: Sun, 04 Nov 2007 17:22:00 -0000 [thread overview]
Message-ID: <200711041721.lA4HLvsx030247@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <m3ir4tbgxz.fsf@codesourcery.com> from "Jim Blandy" at Oct 26, 2007 04:21:28 PM
Jim Blandy wrote:
> Here's a change to dwarf2loc.c that pulls out the guts of the code to
> find a function symbol's frame base expression into its own function.
> We'll also use this function to find frame bases for variables we're
> collecting at a tracepoint, in a later patch. There should be no
> change in behavior. Tested on i386 Linux with no regressions.
Nice; I assume you'll be using that to handle DW_OP_fbreg properly and
get rid of the gdbarch_virtual_frame_pointer call in tracepoint_var_ref?
> +/* Find the frame base expression for PC, within FUNCTION.
> + Set *START to a pointer to it; set *LENGTH to its length. */
> +static void
> +symbol_frame_base (struct symbol *function, CORE_ADDR pc,
> + gdb_byte **start, size_t *length)
I think the FUNCTION is redundant here, it can be recovered
via find_pc_function (pc). This should in all cases have the
same result as the get_frame_function (frame) call below.
> + struct symbol *framefunc = get_frame_function (frame);
> + CORE_ADDR pc = get_frame_address_in_block (frame);
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-11-04 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 23:42 Jim Blandy
2007-10-27 8:19 ` Michael Snyder
2007-11-04 17:22 ` Ulrich Weigand [this message]
2007-11-05 16:41 ` Jim Blandy
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=200711041721.lA4HLvsx030247@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.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