From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12831 invoked by alias); 4 May 2007 15:42:40 -0000 Received: (qmail 12821 invoked by uid 22791); 4 May 2007 15:42:39 -0000 X-Spam-Check-By: sourceware.org Received: from slogw.pt.com (HELO slogw.pt.com) (206.169.14.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 04 May 2007 15:42:36 +0000 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: Is this the right list... Date: Fri, 04 May 2007 15:42:00 -0000 Message-ID: <0F6E41788631664DBE8DF13D06298FE194B7@sloexchange01.corp.pt.com> From: "Jude Moersdorf" To: "aladdin" , X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-05/txt/msg00014.txt.bz2 =46rom the command line try sending a SIGSTOP to the process. 'kill -SIGSTOP ' -----Original Message----- From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On Behalf Of aladdin Sent: Thursday, May 03, 2007 7:04 PM To: gdb@sourceware.org Subject: Re: Is this the right list... Actually, I did (always do) RTFM before posting. I've found that to be less=20 hassle than subscribing to a list, but realize I may be in the minority with=20 that opinion;-). gdb is still attached to the program. The program forks itself twice turning=20 itself into a daemon, and gdb is set to follow the child fork. It seems to=20 do this fine. Obviously, I would normally have set breakpoints to capture=20 it, but forgot to do so in one case, and figured there must be a way to get=20 gdb's attention again. Neither ctl-c nor kill worked; I had to "kill -9" it. I don't understand=20 that; the only signal the user program is catching is SIGALRM (14?). On Thursday 03 May 2007 21:40, Joel Brobecker wrote: > [yes, you can send questions about using GDB to this] > > > When a program goes off into a daemon, or an endless loop or whatever, > > how do you get gdb attention (i. e., get a prompt so you can > > stop/check/abort the program)? > > If GDB is still attached to your program, hitting control-c should > interrupt your program and allow you to see where it is. Otherwise, > your other option, if you are not attach, then just get the pid of > your program, and attach GDB to it using "attach ". > > The GDB documentation should provide you more details about this. > (my very first lesson at engineering school was RTFM :-)