From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14436 invoked by alias); 18 Jan 2002 14:10:23 -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 14386 invoked from network); 18 Jan 2002 14:10:16 -0000 Received: from unknown (HELO TheWorld.com) (199.172.62.104) by sources.redhat.com with SMTP; 18 Jan 2002 14:10:16 -0000 Received: from shell.TheWorld.com (root@shell01.TheWorld.com [199.172.62.241]) by TheWorld.com (8.9.3/8.9.3) with ESMTP id JAA19971; Fri, 18 Jan 2002 09:10:15 -0500 Received: from localhost (qqi@localhost) by shell.TheWorld.com (8.9.3/8.9.3) with ESMTP id JAA8981946; Fri, 18 Jan 2002 09:10:14 -0500 (EST) X-Authentication-Warning: shell01.TheWorld.com: qqi owned process doing -bs Date: Fri, 18 Jan 2002 06:10:00 -0000 From: Quality Quorum To: Per Dalgas Jakobsen cc: gdb@sources.redhat.com Subject: Re: gdb daemon In-Reply-To: <3263F6FB8038AB4192220FA7635835DEB84A@ms12.maridan.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-01/txt/msg00210.txt.bz2 On Fri, 18 Jan 2002, Per Dalgas Jakobsen wrote: > Hi > > I have been looking around for a gdb daemon for remote debugging > on i386 targets. > The gdbserver doesn't seem to be exactly what I'm looking for, > but I might have misunderstood - I hope someone can help me with this > one: > > 1) I need to be able to attach a gdb to a remote target ;-) > 2) I would like to use the "load" feature, which (if I understood it > correctly) allows you to start debugging an application on target > without manually uploading it to the target first (the load command > does that for you). > 3) I would like to be able to attach the debugger to an already > running application on target (having the source on host). > 4) It will be nice (but not critical) if one could include it into > the inetd services, allowing several debugging sessions to be started > simultaneously on the same target. > 5) User space debugging is sufficient, but if kernel space debugging > is also possible: COOL!!! It seems to me that there is no way to satisfy your demands except by 1. Modifying gdbserver - to support load and attach functionality 2. Modifying gdb remote protocol and remote.c to support remote process listing and remote attach. IMHO, you can pretty much get by (1)developing minor modification of gdbserver allowing it to optionally execute `continue' upon loading the application and (2) writing a simple script which will ftp appcode and start it under gdb server. It is not going to be as cool but it will cover at least 90% of your needs with a very minor development efforts. > > Regards > Per > Thanks, Aleksey