This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] sigsetjmp/siglongjmp on cygwin
- To: Keith Seitz <keiths at cygnus dot com>
- Subject: Re: [RFC] sigsetjmp/siglongjmp on cygwin
- From: Mark Kettenis <kettenis at science dot uva dot nl>
- Date: 02 Aug 2001 00:56:29 +0200
- Cc: <gdb-patches at sources dot redhat dot com>
- References: <Pine.GSO.4.33.0108011357170.26158-100000@makita.cygnus.com>
Keith Seitz <keiths@cygnus.com> writes:
> Hi,
>
> I would like to discuss what to do about siglongjmp/sigsetjmp. These
> functions were recently added to configure.in:
>
> 2001-07-12 Mark Kettenis <kettenis@gnu.org>
>
> * configure.in: Add check for sigsetjmp.
>
> 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?
> Until the above change, cygwin used setjmp/longjmp, and this patch will
> force gdb to use them again.
>
> I'm open to better ways of dealing with this.
Can't say I like your patch. An alternative would be to #undef
HAVE_SIGSETJMP in the cygwin xm.h file. That isolates this bogosity
nicely in a platform-specific file. Perhaps some other folks have an
opinion on this. If you don't hear anything, feel free to choose a
hack.
Mark