Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Pedro Alves" <pedro@codesourcery.com>,
	        "Nick Roberts" <nickrob@snap.net.nz>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [non-stop] 00/10 non-stop mode
Date: Thu, 19 Jun 2008 13:57:00 -0000	[thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA04E1BD76@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <200806190607.31652.pedro@codesourcery.com>


> > If non-stop is available, under what circumstance would someone choose to
> > use all-stop?
>
> When someone wants all-stop behaviour.

:-)
When we first discussed non-stop debugging, I also thought that once
it was available, there would be no reason for all-stop.
However, after talking to different people, it seems that it can
come down to a matter of taste and that some users prefer all-stop.

Also, from what I understand, non-stop was a necessary step to get
to multi-process. Some of the users I've spoken to didn't actually mind
all-stop within a single process (for threads), as long as multi-process 
was non-stop.

All this to say that it does seem that all-stop may still be chosen by some.

Marc


  reply	other threads:[~2008-06-19 10:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16  1:29 Pedro Alves
2008-06-16  7:13 ` Vladimir Prus
2008-06-17  4:24 ` Nick Roberts
2008-06-18 17:32   ` Pedro Alves
2008-06-18 21:36     ` Nick Roberts
2008-06-18 21:37       ` Pedro Alves
2008-06-19  3:33         ` Nick Roberts
2008-06-19  5:07           ` Pedro Alves
2008-06-19  6:07             ` Nick Roberts
2008-06-19  6:43               ` Pedro Alves
2008-06-19 13:57                 ` Marc Khouzam [this message]
2008-06-19 16:31               ` Daniel Jacobowitz

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=6D19CA8D71C89C43A057926FE0D4ADAA04E1BD76@ecamlmw720.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nickrob@snap.net.nz \
    --cc=pedro@codesourcery.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