From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-24514-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 28645 invoked by alias); 6 Mar 2006 12:01:08 -0000
Received: (qmail 28635 invoked by uid 22791); 6 Mar 2006 12:01:07 -0000
X-Spam-Check-By: sourceware.org
Received: from host217-40-213-68.in-addr.btopenworld.com (HELO SERRANO.CAM.ARTIMI.COM) (217.40.213.68)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 06 Mar 2006 12:01:04 +0000
Received: from rainbow ([192.168.1.165]) by SERRANO.CAM.ARTIMI.COM with Microsoft SMTPSVC(6.0.3790.1830); 	 Mon, 6 Mar 2006 12:01:00 +0000
From: "Dave Korn" <dave.korn@artimi.com>
To: "'Bob Rossi'" <bob@brasko.net>, 	"'Ed Peschko'" <esp5@pge.com>
Cc: <gdb@sourceware.org>
Subject: RE: tracing, attaching to gdb processes
Date: Mon, 06 Mar 2006 12:01:00 -0000
Message-ID: <055601c64115$a2b494a0$a501a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20060306115527.GA17491@brasko.net>
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2006-03/txt/msg00041.txt.bz2

On 06 March 2006 11:55, Bob Rossi wrote:

> 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

  Or have valgrind attach a gdbserver instance to the faulting process, and
then connect locally to _that_ with gdb?

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....