From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16829 invoked by alias); 3 Mar 2003 13:34:30 -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 16822 invoked from network); 3 Mar 2003 13:34:30 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 3 Mar 2003 13:34:30 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18pryb-0007De-00; Mon, 03 Mar 2003 09:35:38 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18pq5I-0003P6-00; Mon, 03 Mar 2003 08:34:24 -0500 Date: Mon, 03 Mar 2003 13:34:00 -0000 From: Daniel Jacobowitz To: msarasa@fh-konstanz.de Cc: gdb@sources.redhat.com Subject: Re: command targe child question , help needed!! Message-ID: <20030303133424.GA13028@nevyn.them.org> Mail-Followup-To: msarasa@fh-konstanz.de, gdb@sources.redhat.com References: <1046685720.3e632818afd48@webmail.fh-konstanz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1046685720.3e632818afd48@webmail.fh-konstanz.de> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-03/txt/msg00047.txt.bz2 On Mon, Mar 03, 2003 at 11:02:00AM +0100, msarasa@fh-konstanz.de wrote: > > I think this is the right command I have to use in order to connect gdb with > an external proccess. As said in the help. > But , this is my case: > I've made a simulator of a whole board with it's processor. I can run it as a > process , and I want to know a little bit more about how to connect that with > gdb. In the documentation there's no more said about how does target child > work , and I would like to know, if it's possible , the way this command > works. > The format of the packets in this communication, the way I have to use it, and > how exactly should I modify a program that reads from a simulated UART, to > take the outputs from the gnu. > It's REALLY important for me a little help with this. If I should explain more > about the simulator or the problem , please tell me!! but answer me anyway!! > > I'm totally stopped at this point. Target child is what you would use to debug the simulator. If you want to debug the simulated processor, then you probably want to support the remote protocol in the simulator and use "target remote". -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer