X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
Date: Thu, 14 Jul 2011 05:43:42 -0400
Message-ID: <CADqjQ-++gmqPU37vNTFoHCQyrMhqsLmt9BKnmNuRysuxem4=og@mail.gmail.com>
Subject: Pthread question for GDB?
From: Jan Chludzinski <jan DOT chludzinski AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

If I'm stepping through main() in GDB, when I step past
pthread_create() should the associated (newly created) thread begin
executing independently of main() (i.e., the "main" thread)?
Executing independently in the background?

Red Hat's GDB documentation says: "In all-stop mode, whenever your
program stops under gdb for any reason, all threads of execution stop,
not just the current thread. This allows you to examine the overall
state of the program, including switching between threads, without
worrying that things may change underfoot. "

I assume "all-stop mode" is the default?

---Jan

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple