From: Daniel Jacobowitz <drow@false.org>
To: ligang@sunnorth.com.cn
Cc: Joel Brobecker <brobecker@adacore.com>,
bjgnu@sunnorth.com.cn, gdb@sourceware.org
Subject: Re: fail to get ra and bp
Date: Thu, 12 Oct 2006 12:54:00 -0000 [thread overview]
Message-ID: <20061012125417.GB32739@nevyn.them.org> (raw)
In-Reply-To: <OFD6B56831.3737EE08-ON48257205.0027E6D7-48257205.0027E707@sunnorth.com.cn>
On Thu, Oct 12, 2006 at 03:17:06PM +0800, ligang@sunnorth.com.cn wrote:
> Do you know which target use .eh_frame to handle call stack?
> Would you please give me more info about .eh_frame or some documents
> describing it?
Most targets supported by GCC use it. It's the same as DWARF CFI, just
with a slightly different encoding to support use at runtime.
> Could I directly call the functions in prologue-value.[hc]?
Take a look at the one port in the tree (maybe two?) which already
uses this code.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-12 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 7:14 ligang
2006-10-12 12:54 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-12 5:21 ligang
2006-10-12 5:39 ` Joel Brobecker
2006-10-12 4:33 bjgnu
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=20061012125417.GB32739@nevyn.them.org \
--to=drow@false.org \
--cc=bjgnu@sunnorth.com.cn \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=ligang@sunnorth.com.cn \
/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