public inbox for
 help / color / mirror / Atom feed
* gdb doesn't notice when a target resumes
@ 2022-05-04 19:46 Tim Newsome
  2022-05-05  8:58 ` Andrew Burgess
  0 siblings, 1 reply; 3+ messages in thread
From: Tim Newsome @ 2022-05-04 19:46 UTC (permalink / raw)
  To: gdb

In a setup like this:
gdb --- OpenOCD --- hardware target

I can download a program, debug, everything is fine. Let's say we're halted
Now something happens that causes the hardware target to be running again
and no longer halted. OpenOCD notices quickly because it polls the target.
But gdb doesn't ever notice that the target was resumed. There doesn't
appear to be a notification packet
OpenOCD to even communicate to gdb that the target has resumed.

Am I missing something? Have people attempted to tackle this problem?


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-05-06 17:45 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-04 19:46 gdb doesn't notice when a target resumes Tim Newsome
2022-05-05  8:58 ` Andrew Burgess
2022-05-06 17:45   ` Tim Newsome

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).