Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Johan Walles <johan.walles@appeal.se>, gdb <gdb@sources.redhat.com>
Subject: Re: create_new_frame() on Linux/IA64
Date: Fri, 13 Sep 2002 13:11:00 -0000	[thread overview]
Message-ID: <1020913201049.ZM19442@localhost.localdomain> (raw)
In-Reply-To: Johan Walles <johan.walles@appeal.se> "create_new_frame() on Linux/IA64" (Sep 13,  5:17pm)

On Sep 13,  5:17pm, Johan Walles wrote:

> I'm trying to insert artificial stack frames in a backtrace using 
> create_new_frame(addr, pc) on Linux/IA64.  The pc parameter is quite 
> obvious, but what should I use for addr?

The frame pointer.  You might find the following bit from ia64-tdep.c
to be useful:

  /* We won't necessarily have a frame pointer and even if we do,
     it winds up being extraordinarly messy when attempting to find
     the frame chain.  So for the purposes of creating frames (which
     is all read_fp() is used for), simply use the stack pointer value
     instead.  */
  set_gdbarch_read_fp (gdbarch, generic_target_read_sp);

However, it turns out that this isn't really sufficient since it's
possible to leave the memory stack pointer fixed, but change the
bsp value in the register stack.  There have been some proposals
(and patches) for dealing with this.  See:

    http://sources.redhat.com/ml/gdb-patches/2002-05/msg00377.html

and the associated thread.

Kevin


      reply	other threads:[~2002-09-13 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13  8:16 Johan Walles
2002-09-13 13:11 ` Kevin Buettner [this message]

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=1020913201049.ZM19442@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=johan.walles@appeal.se \
    /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