From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: [commit] catch-load.exp: Fix racy FAILs [Re: [4/4] RFC: implement catch load and catch unload]
Date: Mon, 20 Feb 2012 08:28:00 -0000 [thread overview]
Message-ID: <20120220062147.GA5193@host2.jankratochvil.net> (raw)
In-Reply-To: <m3ipk09416.fsf@fleche.redhat.com>
On Tue, 24 Jan 2012 22:36:21 +0100, Tom Tromey wrote:
> gdb/testsuite
> * gdb.base/catch-load.exp: New file.
catch unload zardoz
Catchpoint 3 (unload)
(gdb) PASS: gdb.base/catch-load.exp:non-matching unload with stop-on-solib-events: catch unload zardoz
continue
Continuing.
Stopped due to shared library event (no libraries added or removed)
-(gdb) continue
-Continuing.
-Stopped due to shared library event:
- Inferior loaded gdb/testsuite.unix.-m32/gdb.base/catch-load-so.so
-(gdb) PASS: gdb.base/catch-load.exp:non-matching unload with stop-on-solib-events: continue
+c(gdb) FAIL: gdb.base/catch-load.exp:non-matching unload with stop-on-solib-events: continue
testcase gdb/testsuite/gdb.base/catch-load.exp completed in 18 seconds
Checked in, it looks to me like an obvious duplicate entry there.
Thanks,
Jan
http://sourceware.org/ml/gdb-cvs/2012-02/msg00112.html
--- src/gdb/testsuite/ChangeLog 2012/02/19 13:05:27 1.3079
+++ src/gdb/testsuite/ChangeLog 2012/02/20 06:20:27 1.3080
@@ -1,3 +1,9 @@
+2012-02-20 Jan Kratochvil <jan.kratochvil@redhat.com>
+
+ Fix racy FAILs.
+ * gdb.base/catch-load.exp (one_catch_load_test): Remove duplicate
+ "continue" command.
+
2012-02-19 Jan Kratochvil <jan.kratochvil@redhat.com>
Fix for gdbserver non-extended mode.
--- src/gdb/testsuite/gdb.base/catch-load.exp 2012/01/24 21:39:18 1.1
+++ src/gdb/testsuite/gdb.base/catch-load.exp 2012/02/20 06:20:28 1.2
@@ -68,7 +68,6 @@
gdb_test_no_output "set stop-on-solib-events $sostop"
gdb_test "catch $kind" "Catchpoint $decimal \\(.*\\)"
- send_gdb "continue\n"
gdb_test_multiple "continue" "continue" {
-re "Catchpoint $decimal\r\n.*loaded .*/$testfile2.*\r\n.*$gdb_prompt $" {
if {$match} {
prev parent reply other threads:[~2012-02-20 6:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 21:03 [4/4] RFC: implement catch load and catch unload Tom Tromey
2012-01-19 22:04 ` Eli Zaretskii
2012-01-20 15:12 ` Tom Tromey
2012-01-20 17:40 ` Pedro Alves
2012-01-24 17:31 ` Tom Tromey
2012-01-24 19:40 ` Pedro Alves
2012-01-20 17:44 ` Yao Qi
2012-01-20 19:45 ` Pedro Alves
2012-01-24 17:07 ` Tom Tromey
2012-01-24 17:28 ` Marc Khouzam
2012-01-24 18:25 ` Tom Tromey
2012-01-24 18:32 ` Marc Khouzam
2012-01-24 19:15 ` Tom Tromey
2012-01-24 20:36 ` Marc Khouzam
2012-01-24 17:22 ` Tom Tromey
2012-01-24 19:17 ` Pedro Alves
2012-01-24 22:11 ` Tom Tromey
2012-01-25 11:06 ` Regression for gdb.mi/mi-nsmoribund.exp [Re: [4/4] RFC: implement catch load and catch unload] Jan Kratochvil
2012-01-25 11:18 ` Regression for gdb.base/solib-disc.exp [Re: Regression for gdb.mi/mi-nsmoribund.exp] Jan Kratochvil
2012-01-25 17:09 ` Tom Tromey
2012-01-25 17:27 ` Jan Kratochvil
2012-01-25 16:20 ` Regression for gdb.mi/mi-nsmoribund.exp [Re: [4/4] RFC: implement catch load and catch unload] Tom Tromey
2012-02-20 8:28 ` Jan Kratochvil [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=20120220062147.GA5193@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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