This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Ping: Fix memory corruption when using multiple hardware watchpoints.
- From: David Daney <ddaney at avtrex dot com>
- To: gdb-patches at sourceware dot org
- Date: Tue, 16 Sep 2008 11:33:39 -0700
- Subject: Ping: Fix memory corruption when using multiple hardware watchpoints.
This patch:
http://sourceware.org/ml/gdb-patches/2008-09/msg00222.html
Is awaiting review.
It fixes 10 FAILs in the testsuite on x86_64-pc-linux:
--- native-clean/gdb/testsuite/gdb.sum 2008-09-16 10:56:59.000000000 -0700
+++ native-patched/gdb/testsuite/gdb.sum 2008-09-16 11:26:29.000000000 -0700
@@ -1,4 +1,4 @@
-Test Run By daney on Tue Sep 16 10:47:08 2008
+Test Run By daney on Tue Sep 16 11:05:41 2008
Native configuration is x86_64-unknown-linux-gnu
=== gdb tests ===
@@ -11076,16 +11076,16 @@
PASS: gdb.mi/mi-nonstop.exp: w0,i2 stop
PASS: gdb.mi/mi-nonstop.exp: w1,i2 stop
PASS: gdb.mi/mi-nonstop.exp: set condition, 1
-FAIL: gdb.mi/mi-nonstop.exp: w0,i3 stop (timeout)
+PASS: gdb.mi/mi-nonstop.exp: w0,i3 stop
FAIL: gdb.mi/mi-nonstop.exp: thread state, stop on cond breakpoint
FAIL: gdb.mi/mi-nonstop.exp: update varobj, 2
FAIL: gdb.mi/mi-nonstop.exp: check varobj, w1, 1
PASS: gdb.mi/mi-nonstop.exp: stacktrace of running thread
-FAIL: gdb.mi/mi-nonstop.exp: stacktrace of stopped thread
+PASS: gdb.mi/mi-nonstop.exp: stacktrace of stopped thread
FAIL: gdb.mi/mi-nonstop.exp: select first worker thread
-FAIL: gdb.mi/mi-nonstop.exp: ask the second thread to exit
+PASS: gdb.mi/mi-nonstop.exp: ask the second thread to exit
FAIL: gdb.mi/mi-nonstop.exp: wait for thread exit (timeout)
-FAIL: gdb.mi/mi-nonstop.exp: stacktrace of stopped thread
+PASS: gdb.mi/mi-nonstop.exp: stacktrace of stopped thread
Running ../../../src/gdb/testsuite/gdb.mi/mi-pending.exp ...
PASS: gdb.mi/mi-pending.exp: MI pending breakpoint on pendfunc1
PASS: gdb.mi/mi-pending.exp: Run till MI pending breakpoint on pendfunc1
@@ -12806,10 +12806,6 @@
FAIL: gdb.threads/attach-into-signal.exp: detach
FAIL: gdb.threads/attach-into-signal.exp: detach
FAIL: gdb.threads/attach-into-signal.exp: detach
-FAIL: gdb.threads/attach-into-signal.exp: detach
-FAIL: gdb.threads/attach-into-signal.exp: detach
-FAIL: gdb.threads/attach-into-signal.exp: detach
-FAIL: gdb.threads/attach-into-signal.exp: detach
UNRESOLVED: gdb.threads/attach-into-signal.exp: nonthreaded: attach
(pass 2), pending signal catch
PASS: gdb.threads/attach-into-signal.exp: successfully compiled posix
threads test case
PASS: gdb.threads/attach-into-signal.exp: threaded: attach (pass 1),
pending signal catch
@@ -12864,8 +12860,8 @@
PASS: gdb.threads/fork-child-threads.exp: successfully compiled posix
threads test case
PASS: gdb.threads/fork-child-threads.exp: set follow-fork-mode child
PASS: gdb.threads/fork-child-threads.exp: next over fork
-FAIL: gdb.threads/fork-child-threads.exp: get to the spawned thread
-FAIL: gdb.threads/fork-child-threads.exp: two threads found
+PASS: gdb.threads/fork-child-threads.exp: get to the spawned thread
+PASS: gdb.threads/fork-child-threads.exp: two threads found
Running ../../../src/gdb/testsuite/gdb.threads/gcore-thread.exp ...
PASS: gdb.threads/gcore-thread.exp: successfully compiled posix threads
test case
PASS: gdb.threads/gcore-thread.exp: help gcore
@@ -13404,13 +13400,13 @@
=== gdb Summary ===
-# of expected passes 12565
-# of unexpected failures 178
+# of expected passes 12571
+# of unexpected failures 168
# of expected failures 42
# of unknown successes 1
# of known failures 66
# of unresolved testcases 2
# of untested testcases 7
# of unsupported tests 48