This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug testsuite/13859] New: `set non-stop 1' triggers some fails ingdb.threads/watchthreads-reorder.exp
- From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 16 Mar 2012 08:04:35 +0000
- Subject: [Bug testsuite/13859] New: `set non-stop 1' triggers some fails ingdb.threads/watchthreads-reorder.exp
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13859
Bug #: 13859
Summary: `set non-stop 1' triggers some fails in
gdb.threads/watchthreads-reorder.exp
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
AssignedTo: unassigned@sourceware.org
ReportedBy: qiyao@gcc.gnu.org
Classification: Unclassified
When running gdb.threads/watchthreads-reorder.exp in native gdb when displaced
stepping turned on, we got following fails,
FAIL: gdb.threads/watchthreads-reorder.exp: reorder0: continue a (timeout)
FAIL: gdb.threads/watchthreads-reorder.exp: reorder0: continue to breakpoint:
break-at-exit
FAIL: gdb.threads/watchthreads-reorder.exp: reorder1: continue a (timeout)
FAIL: gdb.threads/watchthreads-reorder.exp: reorder1: rwatch unused1_rwatch
FAIL: gdb.threads/watchthreads-reorder.exp: reorder1: rwatch unused2_rwatch
FAIL: gdb.threads/watchthreads-reorder.exp: reorder1: continue b
FAIL: gdb.threads/watchthreads-reorder.exp: reorder1: continue to breakpoint:
break-at-exit
(gdb) PASS: gdb.threads/watchthreads-reorder.exp: reorder0: rwatch
thread2_rwatch
break 364^M
Breakpoint 4 at 0x8049942: file
../../../gdb/gdb/testsuite/gdb.threads/watchthreads-reorder.c, line 364.^M
(gdb) continue^M
Continuing.^M
[New Thread 0x403d9b70 (LWP 1823)]^M
[New Thread 0x405dab70 (LWP 1824)]^M
Stopping GDB PID 1816.^M
Waiting till the threads initialize their TIDs.^M
Thread 1 TID = 1823, thread 2 TID = 1824, PID = 1820.^M
Waiting till the threads get trapped by the watchpoints.^M
Resuming GDB PID 1816.^M
Joining the threads.^M
Hardware read watchpoint 3: thread2_rwatch^M
^M
Value = 0^M
0x08048f9f in thread2_func (unused=0x0) at
../../../gdb/gdb/testsuite/gdb.threads/watchthreads-reorder.c:126^M
126 rwatch_store = thread2_rwatch;^M
(gdb) Hardware read watchpoint 2: thread1_rwatch^M
^M
Value = 0^M
0x08048eb6 in thread1_func (unused=0x0) at
../../../gdb/gdb/testsuite/gdb.threads/watchthreads-reorder.c:100^M
100 rwatch_store = thread1_rwatch;^M
FAIL: gdb.threads/watchthreads-reorder.exp: reorder0: continue a (timeout)
Haven't analyzed these fails carefully yet, but looks like they are caused by
the test case that is unable to parse/match output after displaced stepping is
on. Open this PR against component `testsuite'.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.