From: Eli Zaretskii <eliz@gnu.org>
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
Date: Mon, 04 Nov 2024 15:22:03 +0200 [thread overview]
Message-ID: <86h68nuoas.fsf@gnu.org> (raw)
In-Reply-To: <SN7PR11MB7091C2A060806C3028F9261FE8512@SN7PR11MB7091.namprd11.prod.outlook.com> (klaus.gerlicher@intel.com)
> From: "Gerlicher, Klaus" <klaus.gerlicher@intel.com>
> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
> "aburgess@redhat.com" <aburgess@redhat.com>, "blarsen@redhat.com"
> <blarsen@redhat.com>
> Date: Mon, 4 Nov 2024 10:03:15 +0000
>
> > > 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.
> >
> > Yes, that's much better. Bonus points for showing an example of such
> > output.
>
> The GDB doc has an example right above this text. Is there a way to easily point to this example?
> Should I maybe add a line that says, "see last line of the small example above"?
Yes, thanks.
prev parent reply other threads:[~2024-11-04 13:22 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
2024-10-29 16:53 ` Eli Zaretskii
2024-11-04 10:03 ` Gerlicher, Klaus
2024-11-04 13:22 ` Eli Zaretskii [this message]
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=86h68nuoas.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@redhat.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=klaus.gerlicher@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).