From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31810 invoked by alias); 29 May 2002 16:15:45 -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 31772 invoked from network); 29 May 2002 16:15:37 -0000 Received: from unknown (HELO eagle5.netburner.com) (209.126.159.74) by sources.redhat.com with SMTP; 29 May 2002 16:15:37 -0000 Received: from warppicard (sdsl-66-80-57-85.dsl.lax.megapath.net [66.80.57.85]) by eagle5.netburner.com (8.11.6/8.11.6) with ESMTP id g4TG7VF08978 for ; Wed, 29 May 2002 09:07:31 -0700 Message-Id: <4.2.0.58.20020529085110.020bb1e0@mail.netburner.com> X-Sender: pbreed@mail.netburner.com Date: Wed, 29 May 2002 09:15:00 -0000 To: gdb@sources.redhat.com From: Paul Breed Subject: Remote Stub operation. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-SW-Source: 2002-05/txt/msg00318.txt.bz2 I'm working with a remote serial stub. I completely understand the protocol definition, but I am looking for some input on the logical operation of the system. When my stub starts up the stub setup code has a built in breakpoint where it stops and waits for GDB, this works well. However I would like to have the system start up and run normally while it waits for GDB to connect. How should the stub respond when the application is already running? Is there anyway to have GDB try to stop the target if the normal target connect fails. Paul