On Fri, 27 Nov 2009 15:11:09 +0100, Veaceslav Falico wrote:
> -FAIL: gdb.base/foll-fork.exp: unpatch child, unpatched parent breakpoints
> from child (timeout)
> +PASS: gdb.base/foll-fork.exp: unpatch child, unpatched parent breakpoints
> from child
> -PASS: gdb.base/foll-fork.exp: set follow parent, hit tbreak
> +FAIL: gdb.base/foll-fork.exp: (timeout) set follow parent, hit tbreak
To be ignored, fixed upstream:
http://sourceware.org/ml/gdb-patches/2009-11/msg00573.html
> -PASS: gdb.mi/mi-nsmoribund.exp: resume all, program exited normally
> +FAIL: gdb.mi/mi-nsmoribund.exp: unexpected stop
> -KFAIL: gdb.threads/watchthreads2.exp: gdb can drop watchpoints in
> multithreaded app (PRMS: gdb/10116)
> +PASS: gdb.threads/watchthreads2.exp: all threads incremented x
These are known to be unstable but there some known watch and non-stop
problems so it may not even be a testcase-side bug.
Therefore this test shows no changes/regressions.
Regards,
Jan
