From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16844 invoked by alias); 5 Jul 2005 11:05:32 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 16826 invoked by uid 22791); 5 Jul 2005 11:05:29 -0000 Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 05 Jul 2005 11:05:29 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1DpkoT-0007G8-1y for gdb@sources.redhat.com; Tue, 05 Jul 2005 12:38:01 +0200 Received: from zigzag.lvk.cs.msu.su ([158.250.17.23]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Jul 2005 12:38:01 +0200 Received: from ghost by zigzag.lvk.cs.msu.su with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Jul 2005 12:38:01 +0200 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: gdb suspends itself Date: Tue, 05 Jul 2005 11:05:00 -0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.8.2 X-SW-Source: 2005-07/txt/msg00027.txt.bz2 Klaus Zeitler wrote: > > Hello, > I'm trying to debug a program with approx. 100 threads under Solaris 5.8, > that generates lots of trace data. When I run the program under gdb, > the first few threads are started, then gdb suspends itself and I need to > call 'fg' to resume execution, i.e. the whole thing looks like e.g.: ...... > UMC1-1-> [07-05 10:05:42:981463] 0x7277b0 (tMain ) : Initializing > OSipc > > [6]+ Stopped gdb ./umc.vx > [675]$ fg > gdb ./umc.vx > ---Type to continue, or q to quit--- > [New LWP 29] > logMsg [07-05 10:20:36:924936] (nbapDemon ) : PetDemon create Server > socket on port 45260 ... > > The same happens with gdb 5.3. and 6.1. > This is probably not a gdb problem, but I hope someone can give me a hint > how I should investigate this odd behavior. Try stty -tostop before running gdb. I had such problems because gdb sometimes tries to output messages while not "owning" terminal. The above command tells the terminal to not stop programs in such cases. - Volodya