From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb@sources.redhat.com
Subject: Re: Reporting non-stop support
Date: Mon, 05 May 2008 18:46:00 -0000 [thread overview]
Message-ID: <fvnkle$d9h$1@ger.gmane.org> (raw)
In-Reply-To: <481F356B.2050800@windriver.com>
Pawel Piech wrote:
> I just think this shows how important it is that the client be able to
> use the same protocol to communicate in either mode, and be able to use
> the event data alone to determine what state actually changed on the target.
Heh, I don't think so. Do you really think it's acceptable to have a "non-stop"
checkbox in UI that will not actually work, and find out that it does not work
only when your program stops for the first time -- stopping all threads? I think
this is not acceptable in any way -- regardless of how carefully and politely
gdb phrases "all threads stopped, your real time application is messed up"
information.
- Volodya
next prev parent reply other threads:[~2008-05-05 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 17:03 Vladimir Prus
2008-05-05 16:27 ` Pawel Piech
2008-05-05 18:46 ` Vladimir Prus [this message]
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='fvnkle$d9h$1@ger.gmane.org' \
--to=vladimir@codesourcery.com \
--cc=gdb@sources.redhat.com \
/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