From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: pedro@palves.net, Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Stop notifications when unwindonsignal is on
Date: Tue, 8 Aug 2023 15:45:50 +0100 [thread overview]
Message-ID: <cover.1691505844.git.aburgess@redhat.com> (raw)
First patch just adds some new testsuite infrastructure. Second patch
is where the interesting work is done.
Thanks,
Andrew
---
Andrew Burgess (2):
gdb/testsuite: add mi_info_frame helper proc (and use it)
gdb: MI stopped events when unwindonsignal is on
gdb/infcall.c | 52 ++++++--
gdb/testsuite/gdb.base/unwindonsignal.exp | 7 +-
gdb/testsuite/gdb.compile/compile-cplus.exp | 14 ++-
gdb/testsuite/gdb.compile/compile.exp | 14 ++-
gdb/testsuite/gdb.cp/gdb2495.exp | 7 +-
gdb/testsuite/gdb.mi/mi-cmd-user-context.exp | 12 +-
gdb/testsuite/gdb.mi/mi-condbreak-fail.exp | 118 +++++++++++++------
gdb/testsuite/gdb.mi/mi-condbreak-throw.cc | 38 ++++++
gdb/testsuite/gdb.mi/mi-condbreak-throw.exp | 116 ++++++++++++++++++
gdb/testsuite/gdb.mi/mi-stack.exp | 7 +-
gdb/testsuite/lib/mi-support.exp | 52 ++++++++
11 files changed, 375 insertions(+), 62 deletions(-)
create mode 100644 gdb/testsuite/gdb.mi/mi-condbreak-throw.cc
create mode 100644 gdb/testsuite/gdb.mi/mi-condbreak-throw.exp
base-commit: 066c738ec5d803a080e3da3b0936484a10c8f31b
--
2.25.4
next reply other threads:[~2023-08-08 14:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 14:45 Andrew Burgess [this message]
2023-08-08 14:45 ` [PATCH 1/2] gdb/testsuite: add mi_info_frame helper proc (and use it) Andrew Burgess
2023-08-08 14:45 ` [PATCH 2/2] gdb: MI stopped events when unwindonsignal is on Andrew Burgess
2023-08-10 15:06 ` Thiago Jung Bauermann
2023-08-14 14:50 ` Andrew Burgess
2023-08-15 0:32 ` Thiago Jung Bauermann
2023-08-16 14:28 ` Andrew Burgess
2023-08-18 21:56 ` Thiago Jung Bauermann
2023-08-23 9:33 ` Andrew Burgess
2023-08-29 16:37 ` Simon Marchi
2023-09-08 8:54 ` Andrew Burgess
2023-09-08 10:03 ` 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.1691505844.git.aburgess@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).