From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18506 invoked by alias); 10 Oct 2008 12:54:27 -0000 Received: (qmail 18493 invoked by uid 22791); 10 Oct 2008 12:54:27 -0000 X-Spam-Check-By: sourceware.org Received: from s200aog10.obsmtp.com (HELO s200aog10.obsmtp.com) (207.126.144.124) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 10 Oct 2008 12:53:42 +0000 Received: from source ([164.129.1.35]) (using TLSv1) by eu1sys200aob010.postini.com ([207.126.147.11]) with SMTP; Fri, 10 Oct 2008 12:53:35 UTC Received: from zeta.dmz-eu.st.com (ns2.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 9BD80DAF6; Fri, 10 Oct 2008 12:53:24 +0000 (GMT) Received: from mail1.cro.st.com (mail1.cro.st.com [164.129.40.131]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 6032C4C2B8; Fri, 10 Oct 2008 12:53:24 +0000 (GMT) Received: from crx595.cro.st.com (crx595.cro.st.com [164.129.44.95]) by mail1.cro.st.com (MOS 3.8.7a) with ESMTP id CQA75697 (AUTH "denis pilat"); Fri, 10 Oct 2008 14:54:23 +0200 (CEST) Message-ID: <48EF5043.4000109@st.com> Date: Fri, 10 Oct 2008 12:54:00 -0000 From: Denis PILAT User-Agent: Thunderbird 2.0.0.17 (X11/20080914) MIME-Version: 1.0 To: Daniel Jacobowitz Cc: teawater , gdb-patches Subject: Re: random results with the gdb testsuite References: <48EDCCAD.3060502@st.com> <48EF10DA.9000701@st.com> <20081010123530.GA7167@caradoc.them.org> In-Reply-To: <20081010123530.GA7167@caradoc.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/msg00316.txt.bz2 Daniel Jacobowitz wrote: > 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. > Sorry, I said window but not in the Microsoft sense. I'm using kde in a linux RHEL3. My debugger terminates, but I can't determine how, valgrind detects nothing, it's like if the process is "killed -9".