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: Eli Zaretskii <eliz at is dot elta dot co dot il>
- Subject: Re: [RFC] sigsetjmp/siglongjmp on cygwin
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Thu, 02 Aug 2001 13:25:01 -0400
- Cc: Keith Seitz <keiths at cygnus dot com>,Mark Kettenis <kettenis at science dot uva dot nl>,gdb-patches at sources dot redhat dot com
- References: <Pine.SUN.3.91.1010802095808.28510L-100000@is>
> On Wed, 1 Aug 2001, Keith Seitz wrote:
>
>
>> > [...] 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.
>
>
> Or maybe #define sigsetjmp setjmp etc., again in a Cygwin-specific
> header. You can even make that define be version specific, assuming
> that some future version of Cygwin solves the problem.
Again, I'm not too warm on this.
Remember, the idea is for autoconf to perform a feature based test: is
feature XYZ supported? In the case of the above, the feature question
is: does the system have a useable sigsetjmp()? Unfortunatly, the test
currently asks: does the system have anything looking like sigsetjmp(),
working or not? :-) I think Keith's original patch is the correct fix.
It refines the test so that, for cygwin, it reports back ``no
sigsetjmp()'' is not there (or is broken).
Andrew