From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org, Nick Roberts <nickrob@snap.net.nz>
Subject: Re: Non-stop debugging and automatically stopping the target
Date: Thu, 10 Apr 2008 18:24:00 -0000 [thread overview]
Message-ID: <20080410180944.GB7163@adacore.com> (raw)
In-Reply-To: <20080410175925.GA5379@caradoc.them.org>
> Perhaps there should be a "real-time sensitive" setting, then -
> probably off by default with a nice manual section?
That sounds like a plan to me.
What would we do if the setting was on, though?
- disallow backtrace?
- allow memory reads?
--
Joel
prev parent reply other threads:[~2008-04-10 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 17:59 Daniel Jacobowitz
2008-04-10 18:00 ` Joel Brobecker
2008-04-10 18:10 ` Daniel Jacobowitz
2008-04-10 18:24 ` Joel Brobecker [this message]
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=20080410180944.GB7163@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
/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