This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Handle multiple breakpoint hits in Python interface
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Kevin Pouget <kevin dot pouget at gmail dot com>
- Cc: tromey at redhat dot com, gdb-patches at sourceware dot org
- Date: Mon, 23 May 2011 06:51:24 -0400
- Subject: Re: [PATCH] Handle multiple breakpoint hits in Python interface
- References: <BANLkTik-ffBpfx4BALF5+Y0xSx_NnaCs7g@mail.gmail.com> <BANLkTinWAR40Fp5TsPubiucTOKygJHHZsw@mail.gmail.com> <m3d3jea6ak.fsf@fleche.redhat.com> <BANLkTik0q4iqSUH9B9ue=0uHzbJqjv32yA@mail.gmail.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Kevin Pouget <kevin.pouget@gmail.com>
> Date: Mon, 23 May 2011 05:38:54 -0400
> Cc: gdb-patches@sourceware.org
>
> 2011-04-22 Kevin Pouget <kevin.pouget@st.com>
>
> Handle multiple breakpoint hits in Python interface:
> * gdb.texinfo (Events In Python): Indicate that multiple breakpoint
> may have been hit and rename the variable to breakpoints.
This part is OK, except...
> +@defivar BreakpointEvent breakpoint
> +A reference to the first breakpoint that was hit of type @code{gdb.Breakpoint}.
> +(Legacy support.)
^^^^^^^^^^^^^^^^^
...this. What is that phrase in parens for? Can it be removed?
Thanks.