From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16946 invoked by alias); 13 Oct 2011 13:49:49 -0000 Received: (qmail 16931 invoked by uid 22791); 13 Oct 2011 13:49:46 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 13 Oct 2011 13:49:20 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0LT000G00BIEVK00@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Thu, 13 Oct 2011 15:48:23 +0200 (IST) Received: from HOME-C4E4A596F7 ([84.229.17.178]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LT000FT6BOMT2D0@a-mtaout22.012.net.il>; Thu, 13 Oct 2011 15:48:23 +0200 (IST) Date: Thu, 13 Oct 2011 13:49:00 -0000 From: Eli Zaretskii Subject: Re: [Patch][Python] PR python/13285 Document named constants for frame unwind stop reasons In-reply-to: To: Kevin Pouget Cc: tromey@redhat.com, pmuldoon@redhat.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <8339ex2eaf.fsf@gnu.org> References: X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-10/txt/msg00390.txt.bz2 > From: Kevin Pouget > 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. > +@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. OK with those changes.