From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26667 invoked by alias); 6 Mar 2006 11:55:17 -0000 Received: (qmail 26652 invoked by uid 22791); 6 Mar 2006 11:55:17 -0000 X-Spam-Check-By: sourceware.org Received: from eastrmmtao06.cox.net (HELO eastrmmtao06.cox.net) (68.230.240.33) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 06 Mar 2006 11:55:14 +0000 Received: from localhost.localdomain ([68.9.66.48]) by eastrmmtao06.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060306115510.EGRS9108.eastrmmtao06.cox.net@localhost.localdomain>; Mon, 6 Mar 2006 06:55:10 -0500 Received: from bob by localhost.localdomain with local (Exim 4.52) id 1FGEJD-0005OZ-EF; Mon, 06 Mar 2006 06:55:27 -0500 Date: Mon, 06 Mar 2006 11:55:00 -0000 From: Bob Rossi To: Ed Peschko Cc: gdb@sourceware.org Subject: Re: tracing, attaching to gdb processes Message-ID: <20060306115527.GA17491@brasko.net> References: <20060306052832.GA12829@mdssdev05> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060306052832.GA12829@mdssdev05> User-Agent: Mutt/1.5.9i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-03/txt/msg00040.txt.bz2 On Sun, Mar 05, 2006 at 09:28:32PM -0800, Ed Peschko wrote: > all, > > I had a couple of suggestions for gdb, and was wondering if they had either > been implemented, or were on the 'wish list' to be implemented. > > > 2) attach mode. I've noticed, especially with testing services through xinetd, > that you can't always expect to have a gdb session come up visibly. > > For example, I was testing cvs the other day through valgrind, and it has a > --db-command option for firing up a debugger if a memory leak occurs. > If you are in a shell, this is no big deal. But if the service runs through > something like valgrind, the gdb debugger gets fired up in a non-interactive > place. I'd like to have the ability to attach to the gdb command from a window > and be able to interact with the gdb session from there. For this problem, couldn't you simply have valgrind either start GDB in screen so that you could attach to it when you want, or use a graphical debugger (xterm -e gdb)? Bob Rossi