On Sun, 29 Nov 2009 23:39:59 +0100, Jan Kratochvil wrote:
> Followed the differences found by Qian and verified none of them (did not
> verify the ppc suspicious one) has any regression in GDB testsuite.
Forgot the log FYI.
Regards,
Jan
-result-2.6.31.5-127.fc12.x86_64/gdb
+result-2.6.32-0.53.rc8.496.fc13.x86_64/gdb
*attach*stop* generally unchecked, it should be covered by ptrace-testsuite and
the GDB testcases are currently racy.
-FAIL: gdb.base/follow-child.exp: break
+PASS: gdb.base/follow-child.exp: break
= unstable testcase, RH-specific, dropped as redundant to other
testcases
/root/jkratoch/redhat/gdb-7.0-3.fc12.src/gdb-7.0-m64/gdb/testsuite
-PASS: gdb.threads/attachstop-mt.exp: attach4 stop by interrupt
-PASS: gdb.threads/attachstop-mt.exp: attach4, exit leaves process sleeping
+FAIL: gdb.threads/attachstop-mt.exp: attach4 stop by interrupt (timeout)
+FAIL: gdb.threads/attachstop-mt.exp: attach4, exit leaves process sleeping
= racy, ignored
-PASS: gdb.base/foll-fork.exp: default parent follow, no catchpoints
+FAIL: gdb.base/foll-fork.exp: (timeout) default parent follow, no catchpoints
= racy, fixed the testcase upstream
/root/jkratoch/redhat/gdb-7.0-3.fc12.src/gdb-7.0-m64/gdb/testsuite.unix.-m32
-FAIL: gdb.threads/attach-stopped.exp: threaded: attach1, exit leaves process
stopped
+PASS: gdb.threads/attach-stopped.exp: threaded: attach1, exit leaves process
stopped
= racy, ignored
-FAIL: gdb.base/interrupt.exp: continue
+PASS: gdb.base/interrupt.exp: continue
FAIL: gdb.base/interrupt.exp: echo data (timeout)
ERROR: Undefined command "".
UNRESOLVED: gdb.base/interrupt.exp: Send Control-C, second time
FAIL: gdb.base/interrupt.exp: signal SIGINT (the program is no longer running)
-FAIL: gdb.base/interrupt.exp: echo more data (timeout)
-FAIL: gdb.base/interrupt.exp: send end of file
+PASS: gdb.base/interrupt.exp: echo more data
+FAIL: gdb.base/interrupt.exp: send end of file (eof)
= both kernels behave the same - correctly, updated erestart* tests
set, for x86_64-x86_64-i386 (kernel-debugger-inferior) GDB needs a fix:
http://sourceware.org/ml/gdb-patches/2009-11/msg00592.html
-FAIL: gdb.server/ext-run.exp: get process list
+PASS: gdb.server/ext-run.exp: get process list
= upstream gdbserver data corruption
-FAIL: gdb.java/jnpe.exp: next over NPE
+PASS: gdb.java/jnpe.exp: next over NPE
= fixed the testcase in archer
/root/jkratoch/redhat/gdb-7.0-3.fc12.src/gdb-7.0-m32/gdb/testsuite.unix.-m32
-ERROR: Couldn't send info inferior 16 to GDB.
-UNRESOLVED: gdb.base/multi-forks.exp: Did kill 16
+PASS: gdb.base/multi-forks.exp: Run to exit 11
= always ignored by me, IMO racy
-PASS: gdb.threads/attachstop-mt.exp: attach4 stop by interrupt
-PASS: gdb.threads/attachstop-mt.exp: attach4, exit leaves process sleeping
+FAIL: gdb.threads/attachstop-mt.exp: attach4 stop by interrupt (timeout)
+FAIL: gdb.threads/attachstop-mt.exp: attach4, exit leaves process sleeping
= racy, ignored
-FAIL: gdb.cp/constructortest.exp: running to main in runto
PASS: gdb.cp/constructortest.exp: breaking on A::A
-FAIL: gdb.cp/constructortest.exp: continue to breakpoint: First line A
-FAIL: gdb.cp/constructortest.exp: Verify in in-charge A::A
-FAIL: gdb.cp/constructortest.exp: continue to breakpoint: First line A
-FAIL: gdb.cp/constructortest.exp: Verify in not-in-charge A::A
+PASS: gdb.cp/constructortest.exp: continue to breakpoint: First line A
+PASS: gdb.cp/constructortest.exp: Verify in in-charge A::A
+PASS: gdb.cp/constructortest.exp: continue to breakpoint: First line A
+PASS: gdb.cp/constructortest.exp: Verify in not-in-charge A::A
-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 (the program is
no longer running)
-FAIL: gdb.pie/break.exp: run until file:function(4) breakpoint (the program is
no longer running)
-FAIL: gdb.pie/break.exp: run until file:function(3) breakpoint (the program is
no longer running)
-FAIL: gdb.pie/break.exp: run until file:function(2) breakpoint (the program is
no longer running)
-FAIL: gdb.pie/break.exp: run until file:function(1) breakpoint (the program is
no longer running)
-FAIL: gdb.pie/break.exp: run until quoted breakpoint (the program is no longer
running)
-FAIL: gdb.pie/break.exp: run until file:linenum breakpoint (the program is no
longer running)
-FAIL: gdb.pie/break.exp: breakpoint offset +1
-FAIL: gdb.pie/break.exp: step onto breakpoint (the program is no longer
running)
+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
+PASS: gdb.pie/break.exp: breakpoint offset +1
+PASS: gdb.pie/break.exp: step onto breakpoint
= ignored although the two kernels behaved differently - they place
libraries of i386-on-x86_64-kernel PIE binaries differently, possibly different
patchset besides the utrace/non-utrace; sent in off-list mail Message-ID:
<20091127084920.ga20...@host0.dyn.jankratochvil.net> ("Fedora kernels
x86_64->i386 PIE libs change/regression")
-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
-Total of 4292375328 (0xffd87320) bytes bytes 53 chunks^M
+Total of 4292422432 (0xffd92b20) bytes bytes 41 chunks^M
= fixed the testcase upstream
-PASS: gdb.threads/watchthreads.exp: disable 2
+PASS: gdb.threads/watchthreads.exp: disable 3
= racy, ignored
-FAIL: gdb.mi/mi-nsmoribund.exp: unexpected stop
+PASS: gdb.mi/mi-nsmoribund.exp: resume all, program exited normally
= racy, ignored
-PASS: gdb.threads/watchthreads2.exp: all threads incremented x
+KFAIL: gdb.threads/watchthreads2.exp: gdb can drop watchpoints in
multithreaded app (PRMS: gdb/10116)
= racy, ignored
-PASS: gdb.base/structs.exp: value foo<n> returned; return 2 structs-tf-td
+FAIL: gdb.base/structs.exp: value foo<n> returned; return 2 structs-tf-td
= unstable testcase, fixed upstream
FAIL: gdb.gdb/selftest.exp: send SIGINT signal to child process (timeout)
-PASS: gdb.gdb/selftest.exp: backtrace through signal handler
+FAIL: gdb.gdb/selftest.exp: backtrace through signal handler
= ptrace unrelated, racy, bug invoked by packaging, fixed upstream
