From: Kevin Pouget <kevin.pouget@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, pmuldoon@redhat.com, gdb-patches@sourceware.org
Subject: Re: [Patch][Python] PR python/13285 Document named constants for frame unwind stop reasons
Date: Thu, 13 Oct 2011 14:06:00 -0000 [thread overview]
Message-ID: <CAPftXUKzaMcT6Dy6ikyYsMWMH8ayhYFPuZyCfL8+9aOr=MdYMQ@mail.gmail.com> (raw)
In-Reply-To: <8339ex2eaf.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
On Thu, Oct 13, 2011 at 3:48 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Kevin Pouget <kevin.pouget@gmail.com>
> > Date: Thu, 13 Oct 2011 14:39:16 +0200
> > Cc: pmuldoon@redhat.com, gdb-patches@sourceware.org
> >
> > I've prepared a bit of documentation for these named constants, based
> > on their comments in the source code.
>
> Thanks.
>
> > +@table @code
> > +@item gdb.FRAME_UNWIND_NO_REASON
> > +No particular reason.
>
> This begs for some explanation of when this "no-reason" reason will be
> seen. Is it true that this value is used when it's NOT impossible to
> find more frames? If so, we should say that explicitly.
Yes, that's my understanding too. I've changed the sentence to
> No particular reason (older frames should be available).
I'll commit the patch in an hour, if no one contradicts
> > +@end table
>
> There's no need to make each value a separate @table. You can just
> make them all be a single table, like this:
>
> @table @code
> @item foo
> Description of foo.
> @item bar
> Description of bar.
> ...
> @end @table.
sorry, I don't know where I got it from !
2011-10-13 Kevin Pouget <kevin.pouget@st.com>
PR python/13285 Document named constants for frame unwind stop reasons
* gdb.texinfo (Frames In Python): Document gdb.FRAME_UNWIND_*
constants.
[-- Attachment #2: gdb.texinfo.patch --]
[-- Type: text/x-patch, Size: 1563 bytes --]
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index da04e2e..0aa90eb 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -23414,7 +23414,39 @@ newest frame.
Return an integer representing the reason why it's not possible to find
more frames toward the outermost frame. Use
@code{gdb.frame_stop_reason_string} to convert the value returned by this
-function to a string.
+function to a string. The value can be one of:
+
+@table @code
+@item gdb.FRAME_UNWIND_NO_REASON
+No particular reason (older frames should be available).
+
+@item gdb.FRAME_UNWIND_NULL_ID
+The previous frame's analyzer returns an invalid result.
+
+@item gdb.FRAME_UNWIND_OUTERMOST
+This frame is the outermost.
+
+@item gdb.FRAME_UNWIND_UNAVAILABLE
+Cannot unwind further, because that would require knowing the
+values of registers or memory that have not been collected.
+
+@item gdb.FRAME_UNWIND_INNER_ID
+This frame ID looks like it ought to belong to a NEXT frame,
+but we got it for a PREV frame. Normally, this is a sign of
+unwinder failure. It could also indicate stack corruption.
+
+@item gdb.FRAME_UNWIND_SAME_ID
+This frame has the same ID as the previous one. That means
+that unwinding further would almost certainly give us another
+frame with exactly the same ID, so break the chain. Normally,
+this is a sign of unwinder failure. It could also indicate
+stack corruption.
+
+@item gdb.FRAME_UNWIND_NO_SAVED_PC
+The frame unwinder did not find any saved PC, but we needed
+one to unwind further.
+@end table
+
@end defun
@defun Frame.pc ()
next prev parent reply other threads:[~2011-10-13 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 12:39 Kevin Pouget
2011-10-13 13:49 ` Eli Zaretskii
2011-10-13 14:06 ` Kevin Pouget [this message]
2011-10-14 11:57 ` Kevin Pouget
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='CAPftXUKzaMcT6Dy6ikyYsMWMH8ayhYFPuZyCfL8+9aOr=MdYMQ@mail.gmail.com' \
--to=kevin.pouget@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=tromey@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