Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Nenad Vukicevic <nenad@intrepid.com>
Subject: Re: Continue does not continue all threads in all-stop mode
Date: Wed, 17 Feb 2010 03:42:00 -0000	[thread overview]
Message-ID: <201002170342.08414.pedro@codesourcery.com> (raw)
In-Reply-To: <4B7B5924.9010709@intrepid.com>

On Wednesday 17 February 2010 02:49:08, Nenad Vukicevic wrote:
> I am running a head version of GDB (couple of weeks old) and noticed that
> in all-stop mode with multiple inferiors continue command does not continue
> all threads (all threads are processes created by fork(0). Only the current
> thread is being run.
> 

Yeah, that's how the old multi-forks support also behaved,
and I kept that behaviour.

On Wednesday 17 February 2010 02:49:08, Nenad Vukicevic wrote:
> Is this normal or an oversight?

It's expected.  See "help set schedule-multiple".

-- 
Pedro Alves


      reply	other threads:[~2010-02-17  3:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17  2:49 Nenad Vukicevic
2010-02-17  3:42 ` Pedro Alves [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=201002170342.08414.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb@sourceware.org \
    --cc=nenad@intrepid.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