This is the mail archive of the
mailing list for the Cygwin project.
RE: B20.1: Thread support seems to be broken in 'gdb'
- To: <earnie_boyd at yahoo dot com>
- Subject: RE: B20.1: Thread support seems to be broken in 'gdb'
- From: "Jon Leichter" <jon at symas dot com>
- Date: Thu, 21 Oct 1999 19:32:16 -0700
- Cc: <cygwin at sourceware dot cygnus dot com>
I know that Cygwin is not thread safe. I was under the assumption that this
specifically applies to the Cygwin DLL, which I am not using in the sample
that I've provided. My sample is a pure Mingw32 compiled program and does not
use the Cygwin DLL. The resulting binary IS supported because the threads are
managed by Win32 DLLs.
The issue is whether or not (Cygwin's provided) 'gdb' is supposed to handle
threads. As I pointed out, Mingw32's distribution of 'gdb' has no problem
debugging threads. It seems reasonable to expect the same from Cygwin's
> -----Original Message-----
> From: Earnie Boyd [mailto:email@example.com]
> Sent: Thursday, October 21, 1999 7:27 PM
> To: Jon Leichter; firstname.lastname@example.org
> Cc: email@example.com
> Subject: Re: B20.1: Thread support seems to be broken in 'gdb'
> --- Jon Leichter <firstname.lastname@example.org> wrote:
> > I could not find mention of this problem in the Cygwin FAQs or the mailing
> > list.
> You didn't look hard enough. Cygwin is _not_ thread safe.
> > I always get a signal SIGTRAP message whenever I try to debug any threaded
> > application. The rest of the 'gdb' session is completely
> unusable. I can run
> > this program (outside of the debugger) with no problem.
> > I'll point out that the version of 'gdb' provided with Mingw32's
> > package does not have this problem.
> Earnie Boyd <mailto:email@example.com>
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org