Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Thu, 22 Jun 2000 17:11:00 -0400
To: "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: gdb and threads
Message-ID: <20000622171100.A4992@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
References: <61891BA043DED21180920090273F1738E18E72 AT TNINT06>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <61891BA043DED21180920090273F1738E18E72@TNINT06>; from abarr@telogy.com on Thu, Jun 22, 2000 at 04:59:52PM -0400

On Thu, Jun 22, 2000 at 04:59:52PM -0400, Arlen Barr wrote:
>Are threads fully supported with the cygwin gdb?

Yes.  Thread 1 is normally the main thread.  Thread 2 is normally the
signal handling thread and is maintained by gdb.  Thread 3 can be a
thread for handling processes if any have been forked or execed.

I use gdb to debug what's going on in thread 2 all of the time.

Other threads pop up when there is a Windows signal or exception.
This is standard Windows behavior.

Btw, if you are not already doing so, you should be running the
newest cygwin version of gdb.

>I'm stepping through code, and although gdb reports only one thread
>(well it lists two, but the first one does not refer to any source
>file), execution suddenly jumps to a point in libstdc++ (version
>2.10.0) without any apparent reason (and then procedes to segmentation
>fault).  The code crashes at seemly random places (in my code) leading
>me to believe that a cygwin library has spawned a thread which is
>crashing.

If cygwin was spawning a random thread it would be dying somewhere in
the cygwin DLL, not in your code.

I don't have any further insight into what is going on here.  Offhand
it sounds like stack corruption.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com