Hello!

The test was conducted on linux-2.6-utrace utrace-ptrace branch with and 
without CONFIG_UTRACE.
The machine was an Intel x86_64 system. Biarch and other testing are under way. 
Here is the diff, and the results look similar. Detailed logs can be found at,
http://people.redhat.com/~qcai/{noutrace,utrace}/

# diff -u noutrace/gdb.sum utrace/gdb.sum 
--- noutrace/gdb.sum    2009-11-24 04:11:05.439560175 -0500
+++ utrace/gdb.sum      2009-11-24 02:59:54.608446620 -0500
@@ -1,4 +1,4 @@
-Test Run By root on Tue Nov 24 03:19:40 2009
+Test Run By root on Tue Nov 24 02:20:46 2009
 Native configuration is x86_64-unknown-linux-gnu
 
                === gdb tests ===
@@ -3773,7 +3773,7 @@
 PASS: gdb.base/foll-fork.exp: default parent follow, no catchpoints
 PASS: gdb.base/foll-fork.exp: set follow parent
 PASS: gdb.base/foll-fork.exp: explicit show parent follow, no catchpoints
-PASS: gdb.base/foll-fork.exp: explicit parent follow, no catchpoints
+FAIL: gdb.base/foll-fork.exp: (timeout) explicit parent follow, no catchpoints
 PASS: gdb.base/foll-fork.exp: set follow child
 PASS: gdb.base/foll-fork.exp: explicit show child follow, no catchpoints
 PASS: gdb.base/foll-fork.exp: explicit child follow, no catchpoints
@@ -3795,7 +3795,7 @@
 PASS: gdb.base/foll-fork.exp: explicit parent follow, tcatch fork
 PASS: gdb.base/foll-fork.exp: set follow parent
 PASS: gdb.base/foll-fork.exp: set follow parent, tbreak
-FAIL: gdb.base/foll-fork.exp: (timeout) set follow parent, hit tbreak
+PASS: gdb.base/foll-fork.exp: set follow parent, hit tbreak
 PASS: gdb.base/foll-fork.exp: set follow parent, cleanup
 Running ./gdb.base/follow-child.exp ...
 PASS: gdb.base/follow-child.exp: set follow-fork-mode child
@@ -14583,7 +14583,7 @@
 PASS: gdb.threads/attachstop-mt.exp: attach3 to stopped, after setting file
 PASS: gdb.threads/attachstop-mt.exp: attach3 to stopped switch thread
 PASS: gdb.threads/attachstop-mt.exp: attach3 to stopped bt
-FAIL: gdb.threads/attachstop-mt.exp: attach3, exit leaves process stopped
+PASS: gdb.threads/attachstop-mt.exp: attach3, exit leaves process stopped
 PASS: gdb.threads/attachstop-mt.exp: attach4 to stopped, after setting file
 PASS: gdb.threads/attachstop-mt.exp: attach4 to stopped switch thread
 PASS: gdb.threads/attachstop-mt.exp: attach4 to stopped bt
@@ -14604,7 +14604,7 @@
 PASS: gdb.threads/attach-stopped.exp: threaded: set file, before attach1 to 
stopped process (re-read)
 PASS: gdb.threads/attach-stopped.exp: threaded: attach1 to stopped, after 
setting file
 PASS: gdb.threads/attach-stopped.exp: threaded: attach1 to stopped bt
-FAIL: gdb.threads/attach-stopped.exp: threaded: attach1, exit leaves process 
stopped
+PASS: gdb.threads/attach-stopped.exp: threaded: attach1, exit leaves process 
stopped
 PASS: gdb.threads/attach-stopped.exp: threaded: attach2 to stopped, after 
setting file
 PASS: gdb.threads/attach-stopped.exp: threaded: attach2 to stopped bt
 PASS: gdb.threads/attach-stopped.exp: continue (threaded: attach2 continue)
@@ -14619,7 +14619,7 @@
 PASS: gdb.threads/bt-clone-stop.exp: run
 FAIL: gdb.threads/bt-clone-stop.exp: 0x0 entry found
 Running ./gdb.threads/current-lwp-dead.exp ...
-PASS: gdb.threads/current-lwp-dead.exp: continue to breakpoint: fn_return
+FAIL: gdb.threads/current-lwp-dead.exp: continue to breakpoint: fn_return
 Running ./gdb.threads/execl.exp ...
 PASS: gdb.threads/execl.exp: successfully compiled posix threads test case
 PASS: gdb.threads/execl.exp: set breakpoint at execl
@@ -15258,13 +15258,13 @@
 PASS: gdb.threads/watchthreads.exp: successfully compiled posix threads test 
case
 PASS: gdb.threads/watchthreads.exp: watch args[0]
 PASS: gdb.threads/watchthreads.exp: watch args[1]
-PASS: gdb.threads/watchthreads.exp: disable 2
-FAIL: gdb.threads/watchthreads.exp: threaded watch loop
+PASS: gdb.threads/watchthreads.exp: disable 3
+PASS: gdb.threads/watchthreads.exp: threaded watch loop
 PASS: gdb.threads/watchthreads.exp: first watchpoint on args[0] hit
 PASS: gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
 PASS: gdb.threads/watchthreads.exp: watchpoint on args[0] hit in thread
 PASS: gdb.threads/watchthreads.exp: watchpoint on args[1] hit in thread
-FAIL: gdb.threads/watchthreads.exp: combination of threaded watchpoints = 30
+PASS: gdb.threads/watchthreads.exp: combination of threaded watchpoints = 30
 Running ./gdb.threads/watchthreads-reorder.exp ...
 PASS: gdb.threads/watchthreads-reorder.exp: successfully compiled posix 
threads test case
 PASS: gdb.threads/watchthreads-reorder.exp: reorder0: set 
can-use-hw-watchpoints 1
@@ -15472,8 +15472,8 @@
 
                === gdb Summary ===
 
-# of expected passes           14229
-# of unexpected failures       402
+# of expected passes           14232
+# of unexpected failures       399
 # of unexpected successes      2
 # of expected failures         40
 # of untested testcases        19

Thanks!
CAI Qian

Reply via email to