Some test cases in the guality testsuite change between UNSUPPORTED and PASS/FAIL depending on system load. I have observed this today on gcc16.
Dave Korn has posted an analysis here: http://gcc.gnu.org/ml/gcc/2010-04/msg00742.html I concur that we should test for gdb being unable to understand the debug information first. The gdb-test procedure has a fixed set of commands, so there should be no unrelated error message popping up later. -- Summary: The guality testsuite has system-load dependent results Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: amylaar at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44898
