From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCHv3 0/2] Inferior specific breakpoints
Date: Thu, 16 Mar 2023 17:03:43 +0000 [thread overview]
Message-ID: <cover.1678985326.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1674207665.git.aburgess@redhat.com>
Changes in v3:
- Patches #2, #3, and #4 from the previous series have been merged.
- Patch #1 is removed from this series in favour of a future patch
from Pedro as mentioned here:
https://sourceware.org/pipermail/gdb-patches/2023-February/196557.html
- Patch #6 has been removed. The core part of this patch (changing
how the 'start' breakpoint is created) has been merged back into
patch #5. The extra tests added in the old #6 are no longer
relevant and have been dropped. The 'start' command is already
tested in our testsuite, so this extra change should be well tested.
- In patch #5:
+ The docs are unchanged (actually I fixed 'a' to 'an' in one place).
+ Inferior breakpoints are deleted when the inferior is removed,
not when it exits.
+ We still don't filter breakpoint locations based on the inferior
program space, but this is now discussed in the commitmessage.
Bascially doing this opens a huge can of worms. I am working on
this, but see this as a future optimisation rather than a
blocker for this initial change.
+ Pedro's feedback about how inferior specific breakpoints were
deleted has been addressed. Since Pedro's initial feedback I've
fixed how thread-specific breakpoints are deleted (I had
originally just copied this code), and I've now copied the fixed
code.
+ The patch no longer adds inferior specific watchpoints. As
Pedro pointed out this feature would only have had a very
limited niche use case, and I didn't see the value of trying to
include that change in this commit. If a user tries to create
an inferior-specific watchpoint they'll now get an error. We
could change this in the future if we're keen.
Changes in v2:
- Biggest changes are in patch #3, as suggested by Baris, I've now
removed the 'thread' and 'inferior' tags from the end of each
location in the 'info breakpoints' output. The information was
already available in the condition line, so this removes some
duplication. For Ada task conditions I've added a condition line
as this was missing.
- Doc updates in #4 and #5 to fix the issues Eli pointed out. These
all seemed pretty minor so I don't think there should be anything
too surprising there.
- Updated patch #5 based on feedback from Baris, this was all pretty
minor stuff though, formatting, and rewording some error messages,
- Updated patch #6 based on feedback from Baris, this is a minor
test cleanup.
Thanks,
Andrew
---
Andrew Burgess (2):
gdb: cleanup around some set_momentary_breakpoint_at_pc calls
gdb: add inferior-specific breakpoints
gdb/NEWS | 15 ++
gdb/breakpoint.c | 237 ++++++++++++++----
gdb/breakpoint.h | 14 +-
gdb/doc/gdb.texinfo | 72 +++++-
gdb/doc/python.texi | 26 +-
gdb/guile/scm-breakpoint.c | 7 +-
gdb/infcmd.c | 15 +-
gdb/inferior.h | 11 +
gdb/infrun.c | 12 +-
gdb/linespec.c | 4 +-
gdb/mi/mi-cmd-break.c | 11 +-
gdb/mi/mi-main.c | 18 +-
gdb/mi/mi-main.h | 6 +
gdb/python/py-breakpoint.c | 96 ++++++-
gdb/python/py-finishbreakpoint.c | 2 +-
gdb/testsuite/gdb.ada/tasks.exp | 2 +
gdb/testsuite/gdb.linespec/cpcompletion.exp | 4 +-
gdb/testsuite/gdb.linespec/explicit.exp | 1 +
gdb/testsuite/gdb.mi/new-ui-bp-deleted.c | 29 +++
gdb/testsuite/gdb.mi/new-ui-bp-deleted.exp | 108 ++++++++
.../gdb.multi/inferior-specific-bp-1.c | 52 ++++
.../gdb.multi/inferior-specific-bp-2.c | 52 ++++
.../gdb.multi/inferior-specific-bp.exp | 179 +++++++++++++
gdb/testsuite/gdb.python/py-breakpoint.exp | 43 ++++
gdb/testsuite/lib/completion-support.exp | 2 +-
gdb/testsuite/lib/mi-support.exp | 20 +-
26 files changed, 946 insertions(+), 92 deletions(-)
create mode 100644 gdb/testsuite/gdb.mi/new-ui-bp-deleted.c
create mode 100644 gdb/testsuite/gdb.mi/new-ui-bp-deleted.exp
create mode 100644 gdb/testsuite/gdb.multi/inferior-specific-bp-1.c
create mode 100644 gdb/testsuite/gdb.multi/inferior-specific-bp-2.c
create mode 100644 gdb/testsuite/gdb.multi/inferior-specific-bp.exp
base-commit: 5a9affd7b875ac183a66ce41f3f226819f0790ed
--
2.25.4
next prev parent reply other threads:[~2023-03-16 17:03 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 11:25 [PATCH 0/6] " Andrew Burgess
2022-11-28 11:25 ` [PATCH 1/6] gdb/remote: announce thread exit events for remote targets Andrew Burgess
2022-11-28 11:25 ` [PATCH 2/6] gdb/testsuite: don't try to set non-stop mode on a running target Andrew Burgess
2022-11-28 11:25 ` [PATCH 3/6] gdb: fix display of thread condition for multi-location breakpoints Andrew Burgess
2022-12-23 8:37 ` Aktemur, Tankut Baris
2022-11-28 11:25 ` [PATCH 4/6] gdb: error if 'thread' or 'task' keywords are overused Andrew Burgess
2022-11-28 13:10 ` Eli Zaretskii
2022-11-28 11:25 ` [PATCH 5/6] gdb: add inferior-specific breakpoints and watchpoints Andrew Burgess
2022-11-28 13:18 ` Eli Zaretskii
2022-12-23 10:05 ` Aktemur, Tankut Baris
2023-01-19 19:13 ` Andrew Burgess
2023-01-20 13:12 ` Aktemur, Tankut Baris
2022-11-28 11:25 ` [PATCH 6/6] gdb: convert the 'start' breakpoint to use inferior keyword Andrew Burgess
2022-12-23 10:17 ` Aktemur, Tankut Baris
2022-12-23 10:55 ` [PATCH 0/6] Inferior specific breakpoints Aktemur, Tankut Baris
2023-01-20 9:46 ` [PATCHv2 " Andrew Burgess
2023-01-20 9:46 ` [PATCHv2 1/6] gdb/remote: announce thread exit events for remote targets Andrew Burgess
2023-02-02 17:50 ` Pedro Alves
2023-02-04 15:46 ` Andrew Burgess
2023-01-20 9:46 ` [PATCHv2 2/6] gdb/testsuite: don't try to set non-stop mode on a running target Andrew Burgess
2023-02-04 16:22 ` Andrew Burgess
2023-01-20 9:46 ` [PATCHv2 3/6] gdb: fix display of thread condition for multi-location breakpoints Andrew Burgess
2023-02-02 18:13 ` Pedro Alves
2023-02-06 14:48 ` Andrew Burgess
2023-02-06 17:01 ` Pedro Alves
2023-02-07 14:42 ` Andrew Burgess
2023-01-20 9:46 ` [PATCHv2 4/6] gdb: error if 'thread' or 'task' keywords are overused Andrew Burgess
2023-01-20 13:22 ` Eli Zaretskii
2023-02-02 14:08 ` Andrew Burgess
2023-02-02 14:31 ` Eli Zaretskii
2023-02-02 18:21 ` Pedro Alves
2023-02-03 16:41 ` Andrew Burgess
2023-02-04 5:52 ` Joel Brobecker
2023-02-04 15:40 ` Andrew Burgess
2023-02-06 11:06 ` Andrew Burgess
2023-01-20 9:46 ` [PATCHv2 5/6] gdb: add inferior-specific breakpoints and watchpoints Andrew Burgess
2023-01-20 13:25 ` Eli Zaretskii
2023-02-02 19:17 ` Pedro Alves
2023-02-03 16:55 ` Andrew Burgess
2023-02-06 17:24 ` Pedro Alves
2023-02-16 12:56 ` Aktemur, Tankut Baris
2023-01-20 9:46 ` [PATCHv2 6/6] gdb: convert the 'start' breakpoint to use inferior keyword Andrew Burgess
2023-02-16 12:59 ` Aktemur, Tankut Baris
2023-03-16 17:03 ` Andrew Burgess [this message]
2023-03-16 17:03 ` [PATCHv3 1/2] gdb: cleanup around some set_momentary_breakpoint_at_pc calls Andrew Burgess
2023-04-03 14:12 ` Andrew Burgess
2023-03-16 17:03 ` [PATCHv3 2/2] gdb: add inferior-specific breakpoints Andrew Burgess
2023-04-03 14:14 ` [PATCHv4] " Andrew Burgess
2023-05-15 19:15 ` [PATCHv5] " Andrew Burgess
2023-05-30 20:41 ` [PATCHv6] " Andrew Burgess
2023-07-07 10:23 ` [PATCHv7] " Andrew Burgess
2023-08-17 15:53 ` [PUSHEDv8] " Andrew Burgess
2023-08-23 8:06 ` [PUSHED] gdb: add missing notify_breakpoint_modified call Andrew Burgess
2023-08-23 8:19 ` [PUSHED] gdb/testsuite: improve MI support for inferior specific breakpoints Andrew Burgess
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=cover.1678985326.git.aburgess@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@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).