public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug ada/26732] FAIL: gdb.ada/mi_catch_ex.exp: continue to exception catchpoint hit (unknown output after running)
Date: Wed, 14 Oct 2020 10:41:57 +0000 [thread overview]
Message-ID: <bug-26732-4717-nPadaqeYnS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26732-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26732
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
This makes the test pass again:
...
diff --git a/gdb/testsuite/gdb.ada/mi_catch_ex.exp
b/gdb/testsuite/gdb.ada/mi_catch_ex.exp
index 103ec85f86..35efe8ef29 100644
--- a/gdb/testsuite/gdb.ada/mi_catch_ex.exp
+++ b/gdb/testsuite/gdb.ada/mi_catch_ex.exp
@@ -129,6 +129,9 @@ with_test_prefix "scenario 2" {
}
}
+mi_delete_breakpoints
+
+
mi_gdb_test "-catch-exception -e Program_Error" \
"\\^done,bkptno=\"$decimal\",bkpt={.*disp=\"keep\",enabled=\"y\",what=\"`Program_
Error' Ada exception\",.*}" \
"catch Program_Error"
...
That was previously done by mi_run_to_main.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-10-14 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 7:36 [Bug ada/26732] New: " vries at gcc dot gnu.org
2020-10-14 7:39 ` [Bug ada/26732] " vries at gcc dot gnu.org
2020-10-14 8:37 ` vries at gcc dot gnu.org
2020-10-14 10:41 ` vries at gcc dot gnu.org [this message]
2020-10-14 11:13 ` [Bug testsuite/26732] " vries at gcc dot gnu.org
2020-10-14 11:18 ` cvs-commit at gcc dot gnu.org
2020-10-14 11:23 ` vries at gcc dot gnu.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-26732-4717-nPadaqeYnS@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).