From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: gdb-patches@sourceware.org, pedro@codesourcery.com,
tromey@redhat.com, Eli Zaretskii <eliz@gnu.org>
Subject: [commit] gdb.python/py-evthreads.exp regression [Re: [PATCH] Handle multiple breakpoint hits in Python interface]
Date: Fri, 16 Sep 2011 07:55:00 -0000 [thread overview]
Message-ID: <20110916073532.GA396@host1.jankratochvil.net> (raw)
In-Reply-To: <CAPftXULY969XF884iyZWdwxkOjfK96=ucO-1zMQmGAVjWsaMhA@mail.gmail.com>
On Thu, 15 Sep 2011 14:30:21 +0200, Kevin Pouget wrote:
> commited
>
> http://sourceware.org/ml/gdb-cvs/2011-09/msg00085.html
Regressed:
FAIL: gdb.python/py-evthreads.exp: Run to breakpoint 1
FAIL: gdb.python/py-evthreads.exp: reached breakpoint 2
FAIL: gdb.python/py-evthreads.exp: reached breakpoint 3
event type: stop
event type: stop
stop reason: breakpoint
+first breakpoint number: 1
breakpoint number: 1
thread num: 1
-(gdb) PASS: gdb.python/py-evthreads.exp: Run to breakpoint 1
+(gdb) FAIL: gdb.python/py-evthreads.exp: Run to breakpoint 1
I understand gdb.python/py-evthreads.exp has been checked in between your
patch development and its check-in.
Checked in.
Regards,
Jan
http://sourceware.org/ml/gdb-cvs/2011-09/msg00096.html
--- src/gdb/testsuite/ChangeLog 2011/09/15 12:42:30 1.2854
+++ src/gdb/testsuite/ChangeLog 2011/09/16 07:34:26 1.2855
@@ -1,3 +1,8 @@
+2011-09-16 Jan Kratochvil <jan.kratochvil@redhat.com>
+
+ * gdb.python/py-evthreads.exp (Run to breakpoint 1)
+ (reached breakpoint 2, reached breakpoint 3): Update expected output.
+
2011-09-15 Kevin Pouget <kevin.pouget@st.com>
PR Python/12692 Add gdb.selected_inferior() to Python interface.
--- src/gdb/testsuite/gdb.python/py-evthreads.exp 2011/09/13 21:39:59 1.5
+++ src/gdb/testsuite/gdb.python/py-evthreads.exp 2011/09/16 07:34:27 1.6
@@ -55,7 +55,7 @@
gdb_run_cmd
set test "Run to breakpoint 1"
gdb_test_multiple "" $test {
- -re "event type: stop\r\nstop reason: breakpoint\r\nbreakpoint number: 1\r\nthread num: 1\r\n$gdb_prompt $" {
+ -re "event type: stop\r\nstop reason: breakpoint\r\nfirst breakpoint number: 1\r\nbreakpoint number: 1\r\nthread num: 1\r\n$gdb_prompt $" {
pass $test
}
-re "The target does not support running in non-stop mode" {
@@ -64,11 +64,11 @@
}
}
-gdb_test "next" "event type: stop\r\nstop reason: breakpoint\r\nbreakpoint number: 2\r\nthread num: 2" "reached breakpoint 2"
+gdb_test "next" "event type: stop\r\nstop reason: breakpoint\r\nfirst breakpoint number: 2\r\nbreakpoint number: 2\r\nthread num: 2" "reached breakpoint 2"
gdb_test "thread 2" {\[Switching to thread 2 .*}
-gdb_test "next" "event type: stop\r\nstop reason: breakpoint\r\nbreakpoint number: 3\r\nthread num: 3" "reached breakpoint 3"
+gdb_test "next" "event type: stop\r\nstop reason: breakpoint\r\nfirst breakpoint number: 3\r\nbreakpoint number: 3\r\nthread num: 3" "reached breakpoint 3"
gdb_test "thread 3" {\[Switching to thread 3 .*}
next prev parent reply other threads:[~2011-09-16 7:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTik-ffBpfx4BALF5+Y0xSx_NnaCs7g@mail.gmail.com>
2011-04-22 9:34 ` [PATCH] Handle multiple breakpoint hits in Python interface Kevin Pouget
2011-05-19 18:34 ` Tom Tromey
2011-05-23 9:39 ` Kevin Pouget
2011-05-23 10:51 ` Eli Zaretskii
2011-05-23 11:01 ` Kevin Pouget
2011-05-23 11:59 ` Eli Zaretskii
2011-05-27 20:09 ` Tom Tromey
2011-05-30 7:37 ` Kevin Pouget
2011-05-30 7:49 ` Eli Zaretskii
2011-05-30 10:53 ` Kevin Pouget
2011-08-31 17:49 ` Tom Tromey
2011-09-01 8:36 ` Kevin Pouget
2011-09-01 8:52 ` Kevin Pouget
2011-09-01 10:08 ` Pedro Alves
2011-09-01 10:18 ` Eli Zaretskii
2011-09-01 11:41 ` Kevin Pouget
2011-09-01 15:39 ` Pedro Alves
2011-09-01 20:53 ` Eli Zaretskii
2011-09-15 12:34 ` Kevin Pouget
2011-09-16 7:55 ` Jan Kratochvil [this message]
2011-09-16 9:12 ` [commit] gdb.python/py-evthreads.exp regression [Re: [PATCH] Handle multiple breakpoint hits in Python interface] Kevin Pouget
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=20110916073532.GA396@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevin.pouget@gmail.com \
--cc=pedro@codesourcery.com \
--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