Dave Korn wrote:
Michael Eager wrote:
Does anyone have any suggestions on how to get one of
these tests to fail consistently, or a different approach
to finding the cause of the intermittent failures?
Perhaps hack the testsuite to run the tests under gdb, setting a breakpoint
on abort() tha
Dave Korn wrote:
Michael Eager wrote:
Does anyone have any suggestions on how to get one of
these tests to fail consistently, or a different approach
to finding the cause of the intermittent failures?
Perhaps hack the testsuite to run the tests under gdb, setting a breakpoint
on abort() tha
Michael Eager wrote:
> Does anyone have any suggestions on how to get one of
> these tests to fail consistently, or a different approach
> to finding the cause of the intermittent failures?
Perhaps hack the testsuite to run the tests under gdb, setting a breakpoint
on abort() that causes it to
On Tue, 2009-04-07 at 23:45 -0700, Michael Eager wrote:
> I'm running the gcc test suite on powerpc-unknown-eabisim
> on the trunk and I get results which are different from
> one run to the next. When I run the failing tests by
> hand, all pass. Mike Stein also has noted that some of
> the test
Hi --
I'm running the gcc test suite on powerpc-unknown-eabisim
on the trunk and I get results which are different from
one run to the next. When I run the failing tests by
hand, all pass. Mike Stein also has noted that some of
the tests are intermittent failures.
There are only a few test cas
