From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2411 invoked by alias); 4 May 2007 02:04:20 -0000 Received: (qmail 2402 invoked by uid 22791); 4 May 2007 02:04:19 -0000 X-Spam-Check-By: sourceware.org Received: from ms-smtp-04.tampabay.rr.com (HELO ms-smtp-04.tampabay.rr.com) (65.32.5.134) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 04 May 2007 02:04:17 +0000 Received: from [192.168.1.20] (124.161.189.72.cfl.res.rr.com [72.189.161.124]) by ms-smtp-04.tampabay.rr.com (8.13.6/8.13.6) with ESMTP id l4424E20027581 for ; Thu, 3 May 2007 22:04:15 -0400 (EDT) From: aladdin To: gdb@sourceware.org Subject: Re: Is this the right list... Date: Fri, 04 May 2007 02:04:00 -0000 User-Agent: KMail/1.9.1 References: <200705032136.32942.aladdin@csunv.com> <20070504014035.GB3804@adacore.com> In-Reply-To: <20070504014035.GB3804@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705032204.14532.aladdin@csunv.com> 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/msg00013.txt.bz2 Actually, I did (always do) RTFM before posting. I've found that to be less hassle than subscribing to a list, but realize I may be in the minority with that opinion;-). gdb is still attached to the program. The program forks itself twice turning itself into a daemon, and gdb is set to follow the child fork. It seems to do this fine. Obviously, I would normally have set breakpoints to capture it, but forgot to do so in one case, and figured there must be a way to get gdb's attention again. Neither ctl-c nor kill worked; I had to "kill -9" it. I don't understand 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 :-)