public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "anders at janssonsoftware dot se" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27439] Detection of a running target/process
Date: Wed, 24 Feb 2021 07:36:52 +0000	[thread overview]
Message-ID: <bug-27439-4717-4hgn7Nh43A@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27439-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27439

--- Comment #3 from Anders Jansson <anders at janssonsoftware dot se> ---
Thanks for the replies. At least not an obvious solution to this it seems.

Yes i guess it would require some work on the gdb side if additional RSP
commands should be handled. For my use cases (at least as a starting point) i
think it would be sufficient with a "polling" solution perhaps not requiring
any extra RSP. If it was possible to issue a gdb command and make it reevaluate
the target status. Then different MI frontends (Eclipse etc) could issue some
sort of "refresh"-command periodically so the IDEs always presents the correct
state.

1. GDB show target/core is in halted state.
2. Issue "refresh" command.
3. If target/core is running gdb is moved to running state (and sends the
"running MI records"). Otherwise it do nothing.

Will do some experimenting. Only need to get into the GDB code first :)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-02-24  7:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19  9:51 [Bug gdb/27439] New: " anders at janssonsoftware dot se
2021-02-21 16:13 ` [Bug gdb/27439] " simark at simark dot ca
2021-02-23 19:13 ` tromey at sourceware dot org
2021-02-24  7:36 ` anders at janssonsoftware dot se [this message]
2021-02-24 14:06 ` clyon at gcc dot gnu.org

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=bug-27439-4717-4hgn7Nh43A@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).