* Connect to already running target?
@ 2003-06-11 3:26 Fred Viles
2003-06-26 14:49 ` Andrew Cagney
0 siblings, 1 reply; 2+ messages in thread
From: Fred Viles @ 2003-06-11 3:26 UTC (permalink / raw)
To: gdb
Is it possible to connect to an already running remote target with
"target remote" and/or "target async"?
As of GDB 5.0, the answer appears to be no, unless I've just not hit
on the right incantation. If the initial '?' packet gets a 'T'
response, of course GDB assumes the target is stopped. If it gets an
"O" response (which the docs seem to suggest should work), it treats
it as a fatal packet error and a failed connection. If it gets an
empty reply, it reports a packet error but then appears to be waiting
for the target to stop (or just a further reply). But trying to
interrupt the target with ctrl-C doesn't work - the ctrl-C packet is
apparently not sent. Same result if it gets *no* reply, but without
the packet error mesage.
I searched the list archive, but all I came up with is a post from
Andrew dated August 2002 RE dropping "target cisco" support, where he
mentioned that the cisco target supported connecting to a running
target and this should be integrated into the standard remote
targets. Has that happened yet?
- Fred
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Connect to already running target?
2003-06-11 3:26 Connect to already running target? Fred Viles
@ 2003-06-26 14:49 ` Andrew Cagney
0 siblings, 0 replies; 2+ messages in thread
From: Andrew Cagney @ 2003-06-26 14:49 UTC (permalink / raw)
To: fv; +Cc: gdb
> Is it possible to connect to an already running remote target with
> "target remote" and/or "target async"?
>
> As of GDB 5.0, the answer appears to be no, unless I've just not hit
> on the right incantation. If the initial '?' packet gets a 'T'
> response, of course GDB assumes the target is stopped. If it gets an
> "O" response (which the docs seem to suggest should work), it treats
> it as a fatal packet error and a failed connection. If it gets an
> empty reply, it reports a packet error but then appears to be waiting
> for the target to stop (or just a further reply). But trying to
> interrupt the target with ctrl-C doesn't work - the ctrl-C packet is
> apparently not sent. Same result if it gets *no* reply, but without
> the packet error mesage.
>
> I searched the list archive, but all I came up with is a post from
> Andrew dated August 2002 RE dropping "target cisco" support, where he
> mentioned that the cisco target supported connecting to a running
> target and this should be integrated into the standard remote
> targets. Has that happened yet?
Neither have happened.
Andrew
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-06-26 14:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-06-11 3:26 Connect to already running target? Fred Viles
2003-06-26 14:49 ` Andrew Cagney
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).