From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keith Seitz <keiths@cygnus.com>
To: Mark Kettenis <kettenis@science.uva.nl>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: [RFC] sigsetjmp/siglongjmp on cygwin
Date: Wed, 01 Aug 2001 16:03:00 -0000
Message-id: <Pine.GSO.4.33.0108011601060.26158-100000@makita.cygnus.com>
References: <s3iae1jjso2.fsf@soliton.wins.uva.nl>
X-SW-Source: 2001-08/msg00016.html

On 2 Aug 2001, Mark Kettenis wrote:

> Keith Seitz <keiths@cygnus.com> writes:
>
> > To make a long story short, I spent a lot of time trying to track this
> > down. The crux of it is that sigsetjmp/siglongjmp _do_ exist on cygwin,
> > but they are not reliable. I don't know why, but they are not.
>
> Damn!  Any chance of fixing cygwin?

I dunno, but I'm not sure we can just go around telling people to update
cygwin -- or can we?

> > I'm open to better ways of dealing with this.
>
> Can't say I like your patch.

Me either. That's why this is an RFC and not an RFA... :-)

> [...] An alternative would be to #undef
> HAVE_SIGSETJMP in the cygwin xm.h file.  That isolates this bogosity
> nicely in a platform-specific file.

Hmmm.. This might be a better approach. I hate touching configure.in: it
makes everyone recompile all of gdb.

What say others?
Keith