From: Eli Zaretskii <eliz@gnu.org>
To: Keith Seitz <keiths@redhat.com>
Cc: philippe.waroquiers@skynet.be, gdb-patches@sourceware.org
Subject: Re: [RFA] Show locno for 'multi location' breakpoint hit msg+conv var $bkptno $locno.
Date: Sat, 04 Jun 2022 09:23:41 +0300 [thread overview]
Message-ID: <83o7z9aqvm.fsf@gnu.org> (raw)
In-Reply-To: <24da89de-d36f-53c7-fe69-a8c7a1c38caf@redhat.com> (message from Keith Seitz via Gdb-patches on Fri, 3 Jun 2022 13:40:00 -0700)
> Date: Fri, 3 Jun 2022 13:40:00 -0700
> From: Keith Seitz via Gdb-patches <gdb-patches@sourceware.org>
>
> I looked up the history of this patch a bit to understand the motivation
> for querying co-workers... I see Eli commented in the original April
> discussion:
>
> > I'm not sure everyone will want to see the likes of
> >
> > Thread 1 "foobar" hit breakpoint 10.42, some_func () at ...
> >
> > But that's MO; I'd be interested in opinions of others.
>
> Well, I'm not a global maintainer, but I'll chime in with my opinion,
> if everyone will permit me. [Ha! You're already reading it!]
>
> I don't think it is a big deal to see ".42" in the output. Far more
> irritating is not knowing exactly which of the many locations it hit.
> I've always felt this was akin to ambiguous output by GDB. "You hit
> breakpoint X." Oh, wait, that's one of fifty different real breakpoints.
We show the source line where the breakpoint breaks right after this,
so at least some of the ambiguity is resolved by that.
next prev parent reply other threads:[~2022-06-04 6:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 15:53 Philippe Waroquiers
2022-04-17 16:14 ` Eli Zaretskii
2022-04-17 16:27 ` Philippe Waroquiers
2022-04-17 17:55 ` Eli Zaretskii
2022-04-29 16:26 ` Philippe Waroquiers
2022-05-07 5:44 ` Philippe Waroquiers
2022-05-13 16:49 ` Philippe Waroquiers
2022-05-22 18:43 ` Philippe Waroquiers
2022-05-30 19:08 ` Philippe Waroquiers
2022-06-03 20:40 ` Keith Seitz
2022-06-04 6:23 ` Eli Zaretskii [this message]
2022-06-04 17:27 ` Matt Rice
2022-06-04 17:45 ` Philippe Waroquiers
2022-06-04 17:37 ` Philippe Waroquiers
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=83o7z9aqvm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=philippe.waroquiers@skynet.be \
/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).