From: NZG <ngustavson@emacinc.com>
To: gdb-patches@sourceware.org
Subject: Re: request for structure documentation
Date: Tue, 24 Jan 2006 22:52:00 -0000 [thread overview]
Message-ID: <200601241651.16514.ngustavson@emacinc.com> (raw)
In-Reply-To: <200601241629.32011.ngustavson@emacinc.com>
A more specific question:
My code appears to be fixable by either causing the architecture specific
unwind code to return null in frame 0, or by allowing unwind to occur here,
but then setting the id to invalid on the unwound frame, thus preventing it
from printing and stopping the chain of get_prev_frames.
But which is correct? This seems unclear from the comments
thx,
NZG
On Tuesday 24 January 2006 4:29 pm, NZG wrote:
> get_prev_register appears to depend on the value of frame_unwind->this_id,
> but I can't find any documentation for what this element represents.
> Could somebody point me to some documentation or elaborate a bit?
>
> struct frame_unwind
> {
> /* The frame's type. Should this instead be a collection of
> predicates that test the frame for various attributes? */
> enum frame_type type;
> /* Should an attribute indicating the frame's address-in-block go
> here? */
> frame_this_id_ftype *this_id;
> frame_prev_register_ftype *prev_register;
> };
>
>
> thx,
> NZG
next prev parent reply other threads:[~2006-01-24 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 22:30 NZG
2006-01-24 22:52 ` NZG [this message]
2006-01-24 22:55 ` Daniel Jacobowitz
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=200601241651.16514.ngustavson@emacinc.com \
--to=ngustavson@emacinc.com \
--cc=gdb-patches@sourceware.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