This is the mail archive of the
mailing list for the GDB project.
Re: [Patch][Python] PR python/13285 Document named constants for frame unwind stop reasons
On Thu, Oct 13, 2011 at 4:05 PM, Kevin Pouget <email@example.com> wrote:
> On Thu, Oct 13, 2011 at 3:48 PM, Eli Zaretskii <firstname.lastname@example.org> wrote:
>> > From: Kevin Pouget <email@example.com>
>> > Date: Thu, 13 Oct 2011 14:39:16 +0200
>> > Cc: firstname.lastname@example.org, email@example.com
>> > I've prepared a bit of documentation for these named constants, based
>> > on their comments in the source code.
>> > +@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 ?<firstname.lastname@example.org>
> ? ? ? ?PR python/13285 Document named constants for frame unwind stop reasons
> ? ? ? ?* gdb.texinfo (Frames In Python): Document gdb.FRAME_UNWIND_*
> ? ? ? ?constants.