From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Add frame unwinder registrary
Date: Thu, 16 Jan 2003 23:31:00 -0000 [thread overview]
Message-ID: <20030116233100.GA8984@nevyn.them.org> (raw)
In-Reply-To: <3E271A4C.9080506@redhat.com>
On Thu, Jan 16, 2003 at 03:47:08PM -0500, Andrew Cagney wrote:
> [ref: cagney-unwind-20030108-branch]
>
> This patch add the two files frame-unwind.[hc] that implement a simple
> frame unwind registrary.
>
> Given a function that contains the address PC, the method
> frame_unwind_find_by_pc(ARCH,PC) returns methods that can unwind the
> specified function's stack frame.
>
> At present the code knows about two frames:
>
> dummy-frame
> these are the frames that GDB creates when doing an inferior function call.
>
> trad[itional]-frame
> GDB's traditional / original prologe analysis, extra frame info, frame
> saved regs, frame.
That's the name you settled on? Hmm, I like it.
> Architectures can add to this list. On the above branch, the d10v adds
> a rewritten d10v specific frame unwinder. An obvious addition would be
> a CFI frame unwinder.
>
> I'll look to commit this in a few days.
Great. After you do, I'll try to integrate the CFI unwinder with it
and then we can move forward on artificial debug info again.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-01-16 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 20:47 Andrew Cagney
2003-01-16 20:56 ` Andrew Cagney
2003-01-16 23:31 ` Daniel Jacobowitz [this message]
2003-01-17 0:11 ` Andrew Cagney
2003-01-18 17:21 ` Andrew Cagney
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=20030116233100.GA8984@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.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