public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Tim Newsome <tim@sifive.com>
To: gdb <gdb@sourceware.org>
Subject: gdb doesn't notice when a target resumes
Date: Wed, 4 May 2022 12:46:15 -0700	[thread overview]
Message-ID: <CAGDihek-sy77M4+jyxWFOaX90gbJPzTBcgQkuWzN36KZmKzbzw@mail.gmail.com> (raw)

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

I can download a program, debug, everything is fine. Let's say we're halted
somewhere.
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
<https://sourceware.org/gdb/onlinedocs/gdb/Notification-Packets.html#Notification-Packets>
for
OpenOCD to even communicate to gdb that the target has resumed.

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

Tim

             reply	other threads:[~2022-05-04 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 19:46 Tim Newsome [this message]
2022-05-05  8:58 ` Andrew Burgess
2022-05-06 17:45   ` Tim Newsome

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGDihek-sy77M4+jyxWFOaX90gbJPzTBcgQkuWzN36KZmKzbzw@mail.gmail.com \
    --to=tim@sifive.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).