From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-84643-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 6136 invoked by alias); 24 Oct 2011 17:09:18 -0000
Received: (qmail 5906 invoked by uid 22791); 24 Oct 2011 17:09:15 -0000
X-SWARE-Spam-Status: No, hits=-1.2 required=5.0	tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 24 Oct 2011 17:08:59 +0000
Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LTK00C00XFEL800@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Mon, 24 Oct 2011 19:08:58 +0200 (IST)
Received: from HOME-C4E4A596F7 ([77.124.212.197]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LTK00BUJYASC1G0@a-mtaout20.012.net.il>; Mon, 24 Oct 2011 19:08:54 +0200 (IST)
Date: Mon, 24 Oct 2011 17:14:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFC] Python Finish Breakpoints
In-reply-to: <CAPftXUK7CqQJn4GMJzAQS9cyC+oAK84H5gpKaPMCU2ZTyP_eYw@mail.gmail.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <834nyye2qc.fsf@gnu.org>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 8BIT
References: <BANLkTim+YH64zkWvdz2_kVUUj=AJ7v4LKw@mail.gmail.com> <BANLkTi=Eu-5B4YyhP2rGdQXgXbBN-EmLKA@mail.gmail.com> <BANLkTikt2hEUcXkGVH44NaUcwiF1SGdMaw@mail.gmail.com> <BANLkTi=UpgogckTD5MZsW+PC5d2F8X-+jA@mail.gmail.com> <BANLkTi==bj50mZgFKq_qA-+3-2CQA3tBVw@mail.gmail.com> <BANLkTimmYEmvKT_984jYEVZnA5RGFpEgNw@mail.gmail.com> <m34o4qd5lh.fsf@fleche.redhat.com> <BANLkTinZ3DSVPRvSiFydCuYs71-DM5-aOg@mail.gmail.com> <m3vcwvubry.fsf@fleche.redhat.com> <BANLkTinBg76_-9i5n=VA2NXp+ZF978J=ig@mail.gmail.com> <m3y5wfl7ky.fsf@fleche.redhat.com> <CAPftXUKHxpww_pEcsMruR6rqo40xw9q9Jzn65-dXys_COt6JbQ@mail.gmail.com> <CAPftXUKsSSb=36CQ+ptGenkt4Q167TtJXuDD2fkU7KFYDu_tPQ@mail.gmail.com> <E1RIK8y-0002Nm-AJ@fencepost.gnu.org> <CAPftXUK7CqQJn4GMJzAQS9cyC+oAK84H5gpKaPMCU2ZTyP_eYw@mail.gmail.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2011-10/txt/msg00646.txt.bz2

> From: Kevin Pouget <kevin.pouget@gmail.com>
> Date: Mon, 24 Oct 2011 16:26:28 +0200
> Cc: tromey@redhat.com, gdb-patches@sourceware.org
> 
> I can add something like
> @menu
> ...
> * Finish Breakpoints in Python:: Setting Breakpoints on function
> return using Python
> ...
> @node Finish Breakpoints in Python
> 
> but can you/Tom confirm that you're happy with a new page/entry menu
> for Finish Breakpoints?

It's okay, but please format it like this:

* Finish Breakpoints in Python:: Setting Breakpoints on function return
                                 using Python

and make sure you use only blanks, not TABs, to indent the second
line.

> It doesn't compile without the menu entry.

Yes, you need that for the Texinfo structuring commands to be happy.

> >> +In some circonstances (e.g.@: @code{longjmp}, C++ exceptions, @value{GDBN}
> >           ^^^^^^^^^^^^^
> > A typo.  Also, we use "C@{++}" throughout the document, it looks
> > prettier in print.
> 
> just for the record, it's "C@t{++}" which works

Yes, of course.  It was a typo on my part ;-)

> I've also prepared a NEWS entry (I'll merge it with the next code
> update). I assume the order is not important and put it next to the
> other breakpoint-related entry; let me know if it's not the right
> place:

It's fine, thanks.