Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFAv2] Show locno for 'multi location' breakpoint hit msg+conv var $bkptno $locno.
Date: Tue, 07 Jun 2022 16:05:26 +0300	[thread overview]
Message-ID: <83ilpc7hex.fsf@gnu.org> (raw)
In-Reply-To: <d6d57f1b1c90910834c745802a2b75b3a7a457f8.camel@skynet.be> (message from Philippe Waroquiers on Sun, 05 Jun 2022 21:44:27 +0200)

> From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Cc: gdb-patches@sourceware.org
> Date: Sun, 05 Jun 2022 21:44:27 +0200
> 
> To test, I have started
>   emacs -Q  # emacs 27.1
>   M-x gdb
>   /absolute/path/to/gdb --nh -i=mi ~/gdb/littleprogs/zeoes
>   b some_func # this adds a breakpoint with 2 code locations
>   M-x gdb-many-windows
> 
> And the breakpoint window shows:
> Num Type       Disp Enb Addr       Hits What
> 1   breakpoint keep y   <MULTIPLE> 1    in unknown
> 
> Note that I have the same behavior with GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git
> 
> When I create a breakpoint with one code location, this breakpoint is properly shown:
>       Disp Enb Addr               Hits What
> 1   breakpoint keep y   <MULTIPLE>         1    in unknown
> 2   breakpoint keep y   0x00005555555551c6 0    in main of zeoes.c:24

Thanks, this should now be fixed for the upcoming Emacs 28.2.

      parent reply	other threads:[~2022-06-07 13:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05 16:57 Philippe Waroquiers via Gdb-patches
2022-06-05 17:10 ` Eli Zaretskii via Gdb-patches
2022-06-05 19:09   ` Philippe Waroquiers via Gdb-patches
2022-06-05 19:26     ` Eli Zaretskii via Gdb-patches
2022-06-05 19:44       ` Philippe Waroquiers via Gdb-patches
2022-06-06 12:44         ` Eli Zaretskii via Gdb-patches
2022-06-07 13:05         ` Eli Zaretskii via Gdb-patches [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=83ilpc7hex.fsf@gnu.org \
    --to=gdb-patches@sourceware.org \
    --cc=eliz@gnu.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