From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch rfc] Per-frame frame-base
Date: Wed, 26 Mar 2003 22:18:00 -0000 [thread overview]
Message-ID: <3E822738.4070403@redhat.com> (raw)
In-Reply-To: <20030326215841.GA24011@nevyn.them.org>
> On Wed, Mar 26, 2003 at 04:51:13PM -0500, Andrew Cagney wrote:
>
>> >On Wed, Mar 26, 2003 at 03:37:22PM -0500, Andrew Cagney wrote:
>> >
>
>> >>The implementation is very much modeled on the frame-unwind code. Debug
>> >>readers are expected to register their own high level frame-base handler.
>
>> >
>> >
>> >So what will the process for getting a dwarf2-debug-info frame
>> >registered look like?
>
>>
>> The current interface is identical to frame-unwind.
>>
>
>> >How will we figure out that this function has
>> >dwarf2 debug info? It's not trivial... we don't have that information
>> >around any more on a per-PC basis.
>
>>
>> Ask the frame's function's symbol or block.
>
>
> Symbols don't currently have this information, nor do blocks.
Well, at least the partial symtab does, sort of implicit via
read_symtab. Shame that location_funcs stuff wasn't a symbol wide
virtual function table.
Andrew
next prev parent reply other threads:[~2003-03-26 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 20:37 Andrew Cagney
2003-03-26 21:00 ` Daniel Jacobowitz
2003-03-26 21:51 ` Andrew Cagney
2003-03-26 21:58 ` Daniel Jacobowitz
2003-03-26 22:18 ` Andrew Cagney [this message]
2003-03-26 22:22 ` Daniel Jacobowitz
2003-04-01 19:25 ` 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=3E822738.4070403@redhat.com \
--to=ac131313@redhat.com \
--cc=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