public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Show locno for 'multi location' breakpoint hit msg+conv var $bkptno $locno.
Date: Sun, 17 Apr 2022 20:55:14 +0300	[thread overview]
Message-ID: <83a6cjy4ql.fsf@gnu.org> (raw)
In-Reply-To: <b105a5269fe614102ddcc5a8c6d37de011e2d310.camel@skynet.be> (message from Philippe Waroquiers on Sun, 17 Apr 2022 18:27:54 +0200)

> From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Cc: gdb-patches@sourceware.org
> Date: Sun, 17 Apr 2022 18:27:54 +0200
> 
> > Thanks.  I think this should be an optional feature.  Not everyone is
> > interested in the particular location that breaks.  Having to disable
> > the breakpoints by locations is definitely an annoyance.
> 
> For the GDB CLI, when the above message is displayed, 
> the user can decide to type
>    disable 1
> or
>    disable 1.2
> or can define aliases such as
>    alias bdisable = disable $bkptno
>    alias ldisable = disable $bkptno.$locno
> to disable the complete breakpoint or only the specific location.

This was not clear from the description.  I think we should make it
clear in the manual.

> I might submit a later patch to define the above aliases by default,
> so that disabling the last breakpoint or location will imply only to 
> type 'bd' or 'ld'.
> 
> Similarly, a front end using MI will (by default) just skip the new locno field.
> So, I am not sure to understand what is the annoyance.

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.

  reply	other threads:[~2022-04-17 17:55 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 [this message]
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
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=83a6cjy4ql.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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).