public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug dap/30678] DAP Server: Extra breakpoint appears when function breakpoint is hit
Date: Tue, 01 Aug 2023 18:56:04 +0000 [thread overview]
Message-ID: <bug-30678-4717-kkGRA0gcbL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30678-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30678
--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8a8a5ccadd18b9f1ecb7943bf56fad29c6f529bc
commit 8a8a5ccadd18b9f1ecb7943bf56fad29c6f529bc
Author: Tom Tromey <tromey@adacore.com>
Date: Mon Jul 24 13:28:58 2023 -0600
Do not send "new breakpoint" event when breakpoint is set
When the DAP client sets a breakpoint, gdb currently sends a "new
breakpoint" event. However, Vladimir Makaev discovered that this
causes VSCode to think there are two breakpoints.
This patch changes gdb to suppress the event in this case.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30678
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-01 18:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 18:14 [Bug dap/30678] New: " vmakaev at gmail dot com
2023-07-24 18:15 ` [Bug dap/30678] " vmakaev at gmail dot com
2023-07-24 18:17 ` vmakaev at gmail dot com
2023-07-24 18:47 ` tromey at sourceware dot org
2023-07-24 18:50 ` tromey at sourceware dot org
2023-07-24 19:28 ` tromey at sourceware dot org
2023-07-24 22:29 ` vmakaev at gmail dot com
2023-07-25 12:47 ` tromey at sourceware dot org
2023-07-25 13:50 ` tromey at sourceware dot org
2023-07-26 15:58 ` tromey at sourceware dot org
2023-08-01 18:56 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-01 18:56 ` tromey at sourceware dot org
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=bug-30678-4717-kkGRA0gcbL@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).