GDB Testsuite Results with CONFIG_UTRACE i686

2009-11-25 Thread caiqian 
Hello!

Those are the test results on i686 F12 hosts with and without CONFIG_UTRACE. 
Interesting thing is that the results on quite different on two Intel hosts. 
gdb.sum is from without CONFIG_UTRACE.

Thanks!
CAI Qian

ProLiant DL360 G4p (Intel)

 diff -u gdb.sum gdb-utrace.sum 
--- gdb.sum 2009-11-25 16:11:35.0 +0800
+++ gdb-utrace.sum  2009-11-25 16:10:45.0 +0800
@@ -1,4 +1,4 @@
-Test Run By root on Tue Nov 24 23:58:53 2009
+Test Run By root on Tue Nov 24 23:26:57 2009
 Native configuration is i686-pc-linux-gnu
 
=== gdb tests ===
@@ -748,8 +748,8 @@
 PASS: gdb.base/bigcore.exp: tbreak 269
 PASS: gdb.base/bigcore.exp: continue
 PASS: gdb.base/bigcore.exp: next
-PASS: gdb.base/bigcore.exp: extract next heap (stop at 50)
-PASS: gdb.base/bigcore.exp: extract prev heap (stop at 50)
+PASS: gdb.base/bigcore.exp: extract next heap
+PASS: gdb.base/bigcore.exp: extract prev heap
 PASS: gdb.base/bigcore.exp: save heap size
 PASS: gdb.base/bigcore.exp: grab pid
 PASS: gdb.base/bigcore.exp: signal SIGABRT
@@ -3718,7 +3718,7 @@
 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
-PASS: gdb.base/follow-child.exp: break
+FAIL: gdb.base/follow-child.exp: break
 Running ./gdb.base/foll-vfork.exp ...
 PASS: gdb.base/foll-vfork.exp: set verbose
 PASS: gdb.base/foll-vfork.exp: insert first vfork catchpoint
@@ -13850,18 +13850,18 @@
 PASS: gdb.pie/break.exp: breakpoint at start of multi line if conditional
 PASS: gdb.pie/break.exp: breakpoint at start of multi line while conditional
 PASS: gdb.pie/break.exp: breakpoint info
-PASS: gdb.pie/break.exp: run until function breakpoint
-PASS: gdb.pie/break.exp: run until breakpoint set at a line number
-PASS: gdb.pie/break.exp: run until file:function(6) breakpoint
-PASS: gdb.pie/break.exp: run until file:function(5) breakpoint
-PASS: gdb.pie/break.exp: run until file:function(4) breakpoint
-PASS: gdb.pie/break.exp: run until file:function(3) breakpoint
-PASS: gdb.pie/break.exp: run until file:function(2) breakpoint
-PASS: gdb.pie/break.exp: run until file:function(1) breakpoint
-PASS: gdb.pie/break.exp: run until quoted breakpoint
-PASS: gdb.pie/break.exp: run until file:linenum breakpoint
+FAIL: gdb.pie/break.exp: run until function breakpoint
+FAIL: gdb.pie/break.exp: run until breakpoint set at a line number
+FAIL: gdb.pie/break.exp: run until file:function(6) breakpoint
+FAIL: gdb.pie/break.exp: run until file:function(5) breakpoint
+FAIL: gdb.pie/break.exp: run until file:function(4) breakpoint
+FAIL: gdb.pie/break.exp: run until file:function(3) breakpoint
+FAIL: gdb.pie/break.exp: run until file:function(2) breakpoint
+FAIL: gdb.pie/break.exp: run until file:function(1) breakpoint
+FAIL: gdb.pie/break.exp: run until quoted breakpoint
+FAIL: gdb.pie/break.exp: run until file:linenum breakpoint (the program is no 
longer running)
 PASS: gdb.pie/break.exp: breakpoint offset +1
-PASS: gdb.pie/break.exp: step onto breakpoint
+FAIL: gdb.pie/break.exp: step onto breakpoint (the program is no longer 
running)
 PASS: gdb.pie/break.exp: Temporary breakpoint function
 PASS: gdb.pie/break.exp: Temporary breakpoint function in file
 PASS: gdb.pie/break.exp: Temporary breakpoint line number #1
@@ -15465,8 +15465,8 @@
 
=== gdb Summary ===
 
-# of expected passes   14562
-# of unexpected failures   115
+# of expected passes   14550
+# of unexpected failures   127
 # of expected failures 40
 # of untested testcases18
 # of unsupported tests 7



HP Workstation XW4200 (Intel)

$ diff -u gdb.sum gdb-utrace.sum 
--- gdb.sum 2009-11-25 16:17:09.0 +0800
+++ gdb-utrace.sum  2009-11-25 16:16:51.0 +0800
@@ -1,4 +1,4 @@
-Test Run By root on Wed Nov 25 01:02:04 2009
+Test Run By root on Wed Nov 25 00:26:48 2009
 Native configuration is i686-pc-linux-gnu
 
=== gdb tests ===
@@ -748,8 +748,8 @@
 PASS: gdb.base/bigcore.exp: tbreak 269
 PASS: gdb.base/bigcore.exp: continue
 PASS: gdb.base/bigcore.exp: next
-PASS: gdb.base/bigcore.exp: extract next heap (stop at 50)
-PASS: gdb.base/bigcore.exp: extract prev heap (stop at 50)
+PASS: gdb.base/bigcore.exp: extract next heap
+PASS: gdb.base/bigcore.exp: extract prev heap
 PASS: gdb.base/bigcore.exp: save heap size
 PASS: gdb.base/bigcore.exp: grab pid
 PASS: gdb.base/bigcore.exp: signal SIGABRT
@@ -3718,7 +3718,7 @@
 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
-FAIL: gdb.base/follow-child.exp: break
+PASS: gdb.base/follow-child.exp: break
 Running ./gdb.base/foll-vfork.exp ...
 PASS: gdb.base/foll-vfork.exp: set verbose
 PASS: gdb.base/foll-vfork.exp: insert first vfork catchpoint
@@ -13850,18 +13850,18 @@
 PASS: gdb.pie/break.exp: breakpoint at start of multi line if conditional
 PASS:

Re: GDB Testsuite Results with CONFIG_UTRACE i686

2009-11-25 Thread Jan Kratochvil 
Hi,

the gdb.pie/break.exp change would be worth checking more but this is based on
the old PIE patch with various known problems and for RHEL-6 there will be
a different/new PIE patch implementation.

Also the gdb.base/bigcore.exp and gdb.base/follow-child.exp changes would be
worth checking if the change is stable across multiple runs of the specific
testcase.

You can also check gdb.log differences, sometimes it is apparent the change is
OK.  Otherwise if the change is stable across multiple runs and it is not
obvious to you why it did change as you already have the machine ready could
you please provide the hostname/password/etc. there?


Thanks,
Jan