Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Handle multiple breakpoint hits in Python interface
Date: Thu, 01 Sep 2011 10:18:00 -0000	[thread overview]
Message-ID: <E1Qz4G6-0006mK-Uf@fencepost.gnu.org> (raw)
In-Reply-To: <CAPftXULfb=M0qzO5tYhE_7+Qo6xj62tAT9xeS6tNdMnFepoyTw@mail.gmail.com>	(message from Kevin Pouget on Thu, 1 Sep 2011 10:35:42 +0200)

> From: Kevin Pouget <kevin.pouget@gmail.com>
> Date: Thu, 1 Sep 2011 10:35:42 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
> 
> +  ** The "gdb.breakpoint" function has been deprecated and in favor of
> +     "gdb.breakpoints".

Without the "and", this is okay.

> +@code{gdb.BreakpointEvent} event indicates that one or several breakpoints have
                                                   ^^^^^^^^^^^^^^
"one or more"

> +@defivar BreakpointEvent breakpoints
> +A sequence containing references to all the breakpoints (type 
> +@code{gdb.Breakpoint}) that were hit.
>  @xref{Breakpoints In Python}, for details of the @code{gdb.Breakpoint} object.
> +@defivar BreakpointEvent breakpoint

This cannot be right: each @defivar should end with the corresponding
"@end defivar".  Didn't makeinfo bitch at you?

> +A reference to the first breakpoint that was hit of type @code{gdb.Breakpoint}.

As opposed to what? watchpoints, catchpoints etc.?  IOW, why do you
need to mention the type issue?

Thanks.


  parent reply	other threads:[~2011-09-01 10:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTik-ffBpfx4BALF5+Y0xSx_NnaCs7g@mail.gmail.com>
2011-04-22  9:34 ` Kevin Pouget
2011-05-19 18:34   ` Tom Tromey
2011-05-23  9:39     ` Kevin Pouget
2011-05-23 10:51       ` Eli Zaretskii
2011-05-23 11:01         ` Kevin Pouget
2011-05-23 11:59           ` Eli Zaretskii
2011-05-27 20:09       ` Tom Tromey
2011-05-30  7:37         ` Kevin Pouget
2011-05-30  7:49           ` Eli Zaretskii
2011-05-30 10:53             ` Kevin Pouget
2011-08-31 17:49               ` Tom Tromey
2011-09-01  8:36                 ` Kevin Pouget
2011-09-01  8:52                   ` Kevin Pouget
2011-09-01 10:08                     ` Pedro Alves
2011-09-01 10:18                   ` Eli Zaretskii [this message]
2011-09-01 11:41                     ` Kevin Pouget
2011-09-01 15:39                       ` Pedro Alves
2011-09-01 20:53                       ` Eli Zaretskii
2011-09-15 12:34                         ` Kevin Pouget
2011-09-16  7:55                           ` [commit] gdb.python/py-evthreads.exp regression [Re: [PATCH] Handle multiple breakpoint hits in Python interface] Jan Kratochvil
2011-09-16  9:12                             ` 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=E1Qz4G6-0006mK-Uf@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=kevin.pouget@gmail.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