This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Intermittent/non-reproducible gcc testsuite failures

From: Michael Eager <eager at eagercon dot com>
To: GCC <gcc at gcc dot gnu dot org>
Date: Wed, 08 Apr 2009 07:24:54 -0700
Subject: Re: Intermittent/non-reproducible gcc testsuite failures
References: <49DC480B.1040503@eagercon.com> <49DC88F1.2000901@gmail.com>

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() that causes it to dump core?  Then at least you'd be able to get a
backtrace and see some state post-mortem.

Thanks, Ben and Dave. I'll give it a try.

  Of course, being a Heisenbug, it'll probably stop appearing when run under a
debugger!

Ah, yes. Hiding in the shadows.


--
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077

References:
- Intermittent/non-reproducible gcc testsuite failures
  - From: Michael Eager
- Re: Intermittent/non-reproducible gcc testsuite failures
  - From: Dave Korn

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]