From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26406 invoked by alias); 6 May 2004 19:14:55 -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 26392 invoked from network); 6 May 2004 19:14:54 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 6 May 2004 19:14:54 -0000 Received: from drow by nevyn.them.org with local (Exim 4.32 #1 (Debian)) id 1BLoKa-0003xj-Ix; Thu, 06 May 2004 15:14:52 -0400 Date: Thu, 06 May 2004 19:14:00 -0000 From: Daniel Jacobowitz To: Grant Edwards Cc: gdb@sources.redhat.com Subject: Re: How to tell gdb to exit? Message-ID: <20040506191452.GA15113@nevyn.them.org> Mail-Followup-To: Grant Edwards , gdb@sources.redhat.com References: <20040506155013.GB12206@grante.dsl.visi.com> <20040506160943.GA12676@grante.dsl.visi.com> <20040506161646.GA12706@grante.dsl.visi.com> <20040506161858.GA28172@nevyn.them.org> <20040506163520.GA12806@grante.dsl.visi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040506163520.GA12806@grante.dsl.visi.com> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-05/txt/msg00054.txt.bz2 On Thu, May 06, 2004 at 11:35:21AM -0500, Grant Edwards wrote: > On Thu, May 06, 2004 at 12:18:58PM -0400, Daniel Jacobowitz wrote: > > > > My bad. It looks like -target-disconnect works afer all. [of > > > course I swear I tried it before and it didn't.] -gdb-exit > > > still refuses to exit, but it will exit on EOF. > > > > > > So, this seems to work: > > > > > > #!/bin/bash > > > h8300-elf-gdb -interpreter=mi < > > 10-target-select async /dev/ttyS0 > > > 20-target-download test.elf > > > 30-exec-continue > > > 40-target-disconnect > > > EOF > > > > > > I messed around with this on and off for days, and couldn't > > > find the answer, but as soon as I put my foot in my mouth > > > publically, the answer appears. Odd, that. > > > > This will leave your target stopped, presumably. > > Perhaps it tries to stop the target, but it can't. Once the > program starts, the gdb stub is "gone". My app has taken over > the UART for use as console I/O, and it's no longer possible to > communicate with the gdb stub[1]. It would be nice to have > another UART so one could be used for console I/O and the other > for GDB, but such is life. > > > The "disconnect" commandd for the CLI will do the same thing. > > Is that what you want? > > With the CLI, you can only send the disconnect command after > you've stopped the target. In my script above, I'm sending the > disconnect command while the target is still running. I guess > since it's no longer possible to stop the applicaion from gdb, > it keeps running. Try target async-remote? I hadn't realized you were using async in the MI mode; in that case, disconnect will just break the connection. -- Daniel Jacobowitz