On May 2, 4:35pm, David Ronis wrote: > FAIL: gdb.base/completion.exp: (timeout) complete 'file ./Make' > ERROR: Got interactive prompt. > FAIL: gdb.base/completion.exp: (timeout) complete 'file ./gdb.base/compl' > FAIL: gdb.base/completion.exp: (timeout) complete 'info func mar' > FAIL: gdb.base/completion.exp: (timeout) complete 'set follow-fork-mode' > FAIL: gdb.base/corefile.exp: print func2::coremaker_local > FAIL: gdb.base/corefile.exp: backtrace in corefile.exp > ERROR: Got interactive prompt. > FAIL: gdb.base/gcore.exp: re-load generated corefile (incomplete note section) > FAIL: gdb.base/gcore.exp: where in corefile, pattern 1 > FAIL: gdb.base/gcore.exp: corefile restored general registers > FAIL: gdb.base/gcore.exp: corefile restored all registers > FAIL: gdb.base/gcore.exp: capture_command_output failed on print >array_func::local_array. > FAIL: gdb.base/gcore.exp: corefile restored stack array > FAIL: gdb.base/gcore.exp: corefile restored backtrace > FAIL: gdb.base/reread.exp: second pass: breakpoint foo in first file > FAIL: gdb.base/selftest.exp: backtrace through signal handler > FAIL: gdb.c++/annota2.exp: watch triggered on a.x > FAIL: gdb.c++/classes.exp: ptype class Static > FAIL: gdb.c++/classes.exp: calling method for small class > FAIL: gdb.mi/mi-break.exp: insert temp breakpoint at "<fullfilename>":6 (callee4) > FAIL: gdb.mi/mi-console.exp: Hello message (known bug) > FAIL: gdb.mi/mi-simplerun.exp: insert breakpoint at "<fullfilename>":6 (callee4) > FAIL: gdb.mi/mi-stack.exp: stack args listing 0 > FAIL: gdb.mi/mi-stack.exp: stack args listing 1 > FAIL: gdb.mi/mi-stack.exp: stack info-depth > FAIL: gdb.mi/mi-stack.exp: stack info-depth 99 > FAIL: gdb.mi/mi0-break.exp: insert temp breakpoint at "<fullfilename>":6 (callee4) > FAIL: gdb.mi/mi0-console.exp: Hello message (known bug) > FAIL: gdb.mi/mi0-simplerun.exp: insert breakpoint at "<fullfilename>":6 (callee4) > FAIL: gdb.mi/mi0-stack.exp: stack args listing 0 > FAIL: gdb.mi/mi0-stack.exp: stack args listing 1 > FAIL: gdb.mi/mi0-stack.exp: stack info-depth > FAIL: gdb.mi/mi0-stack.exp: stack info-depth 99 > FAIL: gdb.threads/linux-dp.exp: philosopher is distinct: 3 > FAIL: gdb.threads/linux-dp.exp: philosopher is distinct: 4 > FAIL: gdb.threads/pthreads.exp: check backtrace from main thread > FAIL: gdb.threads/pthreads.exp: apply backtrace command to all three threads > > === gdb Summary === > > # of expected passes 8058 > # of unexpected failures 36 > # of unexpected successes 12 > # of expected failures 165 > # of unresolved testcases 10 > # of untested testcases 1 > /home/ronis/gdb-5.2/gdb/testsuite/../../gdb/gdb version 5.2 -nx > > > Slightly better, but still problems. > > On the off chance that none of these are serious enough to keep from > installing, please let me know.
I've never known the testsuite to complete with 0 failures. The thread related failures are somewhat worrisome, but on the whole, I think it's okay to install. Kevin _______________________________________________ Bug-gdb mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gdb
