From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9817 invoked by alias); 10 Oct 2008 12:36:15 -0000 Received: (qmail 9808 invoked by uid 22791); 10 Oct 2008 12:36:14 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 10 Oct 2008 12:35:34 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id EACEC10D32; Fri, 10 Oct 2008 12:35:31 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id CFA3C10D2F; Fri, 10 Oct 2008 12:35:31 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KoHDO-0001wC-Ob; Fri, 10 Oct 2008 08:35:30 -0400 Date: Fri, 10 Oct 2008 12:36:00 -0000 From: Daniel Jacobowitz To: Denis PILAT Cc: teawater , gdb-patches Subject: Re: random results with the gdb testsuite Message-ID: <20081010123530.GA7167@caradoc.them.org> Mail-Followup-To: Denis PILAT , teawater , gdb-patches References: <48EDCCAD.3060502@st.com> <48EF10DA.9000701@st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48EF10DA.9000701@st.com> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-10/txt/msg00314.txt.bz2 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