Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfa] allow unwinding "past main" for dummy frames
Date: Mon, 06 Dec 2004 04:59:00 -0000	[thread overview]
Message-ID: <20041206042736.GA496@nevyn.them.org> (raw)
In-Reply-To: <20041206041458.GF6359@tausq.org>

On Sun, Dec 05, 2004 at 08:14:58PM -0800, Randolph Chung wrote:
> so, what happens is that we call __gcc_plt_call using a stack trampoline
> which tells __gcc_plt_call to return to "current function". after
> __gcc_plt_call calls the callee function, it looks up the return address
> ("current function") and restores the space registers to the correct
> value for that address. ergo, <dummy frame> actually has a frame pc that
> belongs to "current function", and if that's main, dummy frame will
> trigger the inside_main_func check.
> 
> does this make sense?

Some sense, but not good sense.

Can we edit the space registers ourselves?  If so, why don't we rely on
that?  I'm not talking about the call, just the return.  So generate a
call to __gcc_plt_call with a return address anywhere you please, and
after the dummy call when we restore the saved regcache the space
registers will be right again.  So you could just use _start.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-12-06  4:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06  3:31 Randolph Chung
2004-12-06  3:45 ` Daniel Jacobowitz
2004-12-06  4:27   ` Randolph Chung
2004-12-06  4:59     ` Daniel Jacobowitz [this message]
2004-12-06  6:22       ` Randolph Chung
2004-12-06 15:35         ` Daniel Jacobowitz
2004-12-06 16:54           ` Randolph Chung
2004-12-08  3:27           ` Randolph Chung
2004-12-06 14:11       ` Randolph Chung

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=20041206042736.GA496@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=randolph@tausq.org \
    /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