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
Message-ID:	<61891BA043DED21180920090273F1738E18E76@TNINT06>
From:	Arlen Barr <abarr AT telogy DOT com>
To:	"'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Subject:	RE: gdb and threads
Date:	Fri, 23 Jun 2000 09:48:35 -0400
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2448.0)

thanks for the info chris ...

another problem I'm having with gdb is that the "variable balloons" only
show up about half the time.  I can see why it might have problems with c++
classes, but sometimes variables of type 'int' won't even come up (either
intialized or uninitialized)

arlen

(I am using gdb 5.0)

> -----Original Message-----
> From: Chris Faylor [mailto:cgf AT cygnus DOT com]
> Sent: Thursday, June 22, 2000 5:11 PM
> To: 'cygwin AT sourceware DOT cygnus DOT com'
> Subject: Re: gdb and threads
> 
> 
> 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
> 

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

- Raw text -