This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Remote Stub operation.
- From: "William A. Gatliff" <bgat at billgatliff dot com>
- To: Paul Breed <Paul at Netburner dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Wed, 29 May 2002 13:21:29 -0500
- Subject: Re: Remote Stub operation.
- References: <4.2.0.58.20020529085110.020bb1e0@mail.netburner.com>
- Reply-to: bgat at billgatliff dot com
Paul:
If your stub uses interrupt-driven receive, it could just interrupt
the main aplication when it gets the connect commands from gdb.
b.g.
On Wed, May 29, 2002 at 09:23:50AM -0400, Paul Breed wrote:
> 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
>
>
>
>
--
Bill Gatliff
bgat@billgatliff.com