From: "Gerlicher, Klaus" <klaus.gerlicher@intel.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"aburgess@redhat.com" <aburgess@redhat.com>,
"blarsen@redhat.com" <blarsen@redhat.com>
Subject: RE: [PATCH v7 2/2] gdb, breakpoint: output multiple bp locations
Date: Tue, 29 Oct 2024 15:57:47 +0000 [thread overview]
Message-ID: <SN7PR11MB70910EB293954159F3871488E84B2@SN7PR11MB7091.namprd11.prod.outlook.com> (raw)
In-Reply-To: <86v7xb5a33.fsf@gnu.org>
Thanks Eli. Replies inline. I'll wait until I get some feedback from others and will roll fixes into a V8.
Klaus
> -----Original Message-----
> From: Eli Zaretskii <eliz@gnu.org>
> Sent: Tuesday, October 29, 2024 2:10 PM
> To: Gerlicher, Klaus <klaus.gerlicher@intel.com>
> Cc: gdb-patches@sourceware.org; aburgess@redhat.com;
> blarsen@redhat.com
> Subject: Re: [PATCH v7 2/2] gdb, breakpoint: output multiple bp locations
>
> > From: Klaus Gerlicher <klaus.gerlicher@intel.com>
> > Date: Tue, 29 Oct 2024 11:33:43 +0000
> >
> > gdb/NEWS | 4 +
> > gdb/breakpoint.c | 135 ++++++++++++++----
> > gdb/doc/gdb.texinfo | 45 +++++-
> > gdb/testsuite/gdb.base/ctxobj.exp | 4 +-
> > .../run-control-while-bg-execution.exp | 2 +-
> > gdb/testsuite/gdb.cp/ovldbreak.exp | 6 +-
> > gdb/testsuite/gdb.linespec/cpcompletion.exp | 2 +
> > gdb/testsuite/gdb.linespec/linespec.exp | 2 +-
> > gdb/testsuite/gdb.linespec/multiple-locs.cc | 41 ++++++
> > gdb/testsuite/gdb.linespec/multiple-locs.exp | 57 ++++++++
> > .../mi-breakpoint-multiple-locations.exp | 4 +-
> > .../gdb.mi/user-selected-context-sync.exp | 16 +--
> > .../gdb.multi/inferior-specific-bp.exp | 2 +-
> > .../gdb.multi/multi-target-continue.exp | 3 +-
> > .../gdb.multi/multi-target-ping-pong-next.exp | 6 +-
> > gdb/testsuite/gdb.python/py-breakpoint.exp | 3 +-
> > gdb/testsuite/lib/completion-support.exp | 3 +
> > gdb/testsuite/lib/gdb.exp | 34 ++++-
> > 18 files changed, 308 insertions(+), 61 deletions(-)
> > create mode 100644 gdb/testsuite/gdb.linespec/multiple-locs.cc
> > create mode 100644 gdb/testsuite/gdb.linespec/multiple-locs.exp
>
> Thanks.
>
> > --- a/gdb/NEWS
> > +++ b/gdb/NEWS
> > @@ -3,6 +3,10 @@
> >
> > *** Changes since GDB 15
> >
> > +* Printing multiple breakpoint locations when setting a breakpoint that is
> > + instantiated for multiple locations now prints all locations limited by
> > + "set breakpoint max-breakpoint-location-printed <count>".
> > +
> > * Debugging support for Intel MPX has been removed. This includes the
> > removal of
> > ** MPX register support
>
> This part is OK.
>
Thank you.
> > + add_setshow_uinteger_cmd ("max-breakpoint-locations-printed",
> > + class_breakpoint,
> > + &breakpoint_show_max_locations, _("\
> > +Set number of locations printed when setting a breakpoint."), _("\
> > +Show number of locations printed when setting a breakpoint."), _("\
> > +Use this to choose how many number of locations are printed\n\
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Either "how many locations" or "the number of locations".
>
I think I had looked at similar commands and tried to copy something verbatim
and I failed miserably. Thanks for catching this.
> > +@kindex show breakpoint max-breakpoint-locations-printed
> > +@item show breakpoint max-breakpoint-locations-printed
> > +Display the number of locations that @code{break} will print. If the
> number
> > +of locations is greater than the limit, the additional number of locations
> > +will be listed.
> ^^^^^^^^^^^^^^
> I guess "will not be listed"?
>
What I meant to say is that there will be a line of output that tells the user
how many more locations apart from the listed one there are.
So maybe:
"If the number of locations is greater than the limit, the breakpoint command will
add a line reporting the number of locations that were not listed due to the limit.
Or maybe you have a better way of phrasing this?
> The documentation is OK with those nits fixed.
>
> Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2024-10-29 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 11:33 [PATCH v7 0/2] gdb: setting BP with multiple locations only displays one location Klaus Gerlicher
2024-10-29 11:33 ` [PATCH v7 1/2] gdb: extend gdb_breakpoint for multiple locations Klaus Gerlicher
2024-10-29 11:33 ` [PATCH v7 2/2] gdb, breakpoint: output multiple bp locations Klaus Gerlicher
2024-10-29 13:10 ` Eli Zaretskii
2024-10-29 15:57 ` Gerlicher, Klaus [this message]
2024-10-29 16:53 ` Eli Zaretskii
2024-11-04 10:03 ` Gerlicher, Klaus
2024-11-04 13:22 ` Eli Zaretskii
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=SN7PR11MB70910EB293954159F3871488E84B2@SN7PR11MB7091.namprd11.prod.outlook.com \
--to=klaus.gerlicher@intel.com \
--cc=aburgess@redhat.com \
--cc=blarsen@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).