From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: RFC: Mark outer frames
Date: Sat, 29 Aug 2009 07:24:00 -0000 [thread overview]
Message-ID: <83eiqvaz9t.fsf@gnu.org> (raw)
In-Reply-To: <20090828213237.GA9175@caradoc.them.org>
> Date: Fri, 28 Aug 2009 17:32:37 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> gdb/doc/
> * gdbint.texinfo (Unwinding the Frame ID): Reference outer_frame_id.
This part is OK, but the code still has null_frame_id, so perhaps
deleting it entirely here is not really right. How about adding a
sentence explaining how null_frame_id differs from outer_frame_id?
next prev parent reply other threads:[~2009-08-29 6:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 22:16 Daniel Jacobowitz
2009-08-29 7:24 ` Eli Zaretskii [this message]
2009-08-31 22:54 ` Joel Brobecker
2009-09-01 22:41 ` Doug Evans
2009-09-02 17:03 ` Joel Brobecker
2009-09-02 17:33 ` Daniel Jacobowitz
2009-09-03 22:52 ` Joel Brobecker
2009-09-10 2:29 ` [gdb-7.0] " Joel Brobecker
2009-09-10 19:12 ` Daniel Jacobowitz
2009-09-10 22:41 ` Joel Brobecker
2009-09-12 22:13 ` [gdb-7.0/doco] " Joel Brobecker
2009-09-12 22:14 ` Joel Brobecker
2009-09-13 3:11 ` Eli Zaretskii
2009-09-13 16:29 ` Joel Brobecker
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=83eiqvaz9t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--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