Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: 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:10:00 -0000	[thread overview]
Message-ID: <20080410175925.GA5379@caradoc.them.org> (raw)
In-Reply-To: <20080410174124.GA7163@adacore.com>

On Thu, Apr 10, 2008 at 10:41:24AM -0700, Joel Brobecker wrote:
> The subject of this thread says "non-stop" mode, so does it mean that
> in "all-stop" mode we're assuming that the target program is not time-
> sensitive, and so we'll always pause it?

I just wasn't thinking about the problem properly.  Nick's subject
was right; this applies to any async target.

Perhaps there should be a "real-time sensitive" setting, then -
probably off by default with a nice manual section?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-04-10 17:59 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 [this message]
2008-04-10 18:24     ` Joel Brobecker

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=20080410175925.GA5379@caradoc.them.org \
    --to=drow@false.org \
    --cc=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