From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17451 invoked by alias); 10 Oct 2008 17:40:00 -0000 Received: (qmail 17440 invoked by uid 22791); 10 Oct 2008 17:40:00 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 10 Oct 2008 17:39:18 +0000 Received: from mailhost3.vmware.com (mailhost3.vmware.com [10.16.27.45]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 05A284B007; Fri, 10 Oct 2008 10:39:15 -0700 (PDT) Received: from [10.20.92.59] (promb-2s-dhcp59.eng.vmware.com [10.20.92.59]) by mailhost3.vmware.com (Postfix) with ESMTP id EC06DC9A81; Fri, 10 Oct 2008 10:39:14 -0700 (PDT) Message-ID: <48EF92AB.3010306@vmware.com> Date: Fri, 10 Oct 2008 17:40:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: Denis PILAT CC: Daniel Jacobowitz , 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> <48EF5043.4000109@st.com> In-Reply-To: <48EF5043.4000109@st.com> 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/msg00324.txt.bz2 Denis PILAT wrote: > > 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". What happens if you run gdb by hand, and repeat each command from the log?