random results with the gdb testsuite

Daniel Jacobowitz drow@false.org
Fri Oct 10 12:36:00 GMT 2008


On Fri, Oct 10, 2008 at 10:22:50AM +0200, Denis PILAT wrote:
> Here is part of the log file. At a specific time  (p/f *(long long *)) it 
> seems like the debugger hangs up, then all further test are UNRESOLVED.
>
> If I run this test and don't touch my keyboard, don't switch the current  
> window, then it's 100% successful.
>
> If I'm using the console window intensively after having run this test,  
> switching window, using keyboard,  then I get the following log where  
> apparently my debugger crash, or just close.
> I can't find a way to debug that problem.

Normally Windows (you did say this was Windows, right?) can be
configured to pop up a dialog when a program crashes.  You can't
necessarily get into GDB from there, but you may be able to get some
kind of dump.  I think the Cygwin folks have instructions on getting
stack dumps or even core dumps from that point.

-- 
Daniel Jacobowitz
CodeSourcery



More information about the Gdb-patches mailing list