This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] Python Finish Breakpoints


> 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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]