Re: [RFA] Show locno for 'multi location' breakpoint hit msg+conv var $bkptno $locno.

[Philippe Waroquiers <philippe.waroquiers@skynet.be>]

On Sat, 2022-06-04 at 17:27 +0000, Matt Rice via Gdb-patches wrote:
> On Sat, Jun 4, 2022 at 6:23 AM Eli Zaretskii via Gdb-patches
> <gdb-patches@sourceware.org> wrote:
> > 
> > > 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.
> 
> My thoughts are that whether or not source line resolving ambiguity
> printing the breakpoint locno
> may be useful for instance, `disable 10.42` to disable that location,
> you wouldn't have to do
> info break and look through the what or address column of `info b`.
Yes, that was the main trigger to add this change.
As you indicate, if the breakpoint is in an inlined function,
then all locations have the same source and line nr
and the only differentiating aspect is then the address.

Philippe