From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb@sourceware.org
Subject: Reporting non-stop support
Date: Sun, 04 May 2008 17:03:00 -0000 [thread overview]
Message-ID: <200805042102.30612.vladimir@codesourcery.com> (raw)
As discussed before, it would be nice if GDB could report if the current
target supports non-stop, so that frontend can act accordingly (even if
"accordingly" means saying "sorry, non-stop is not supported").
However, it's a bit tricky, because until we do "run", the two
targets on the target stack are dummy target and exec_ops -- neither of
which, naturally, have any clue about non-stop.
It's only when we do "run" when find_default_run_target is called, and
something reasonable is pushed to the target stack. Which means that
until we do "run", we don't know if the target supports non-stop, and
when we do "run", it's a bit too later to set non-stop mode.
Any suggestions?
- Volodya
next reply other threads:[~2008-05-04 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 17:03 Vladimir Prus [this message]
2008-05-05 16:27 ` Pawel Piech
2008-05-05 18:46 ` Vladimir Prus
2008-05-05 19:44 ` Pawel Piech
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=200805042102.30612.vladimir@codesourcery.com \
--to=vladimir@codesourcery.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