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: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: [RFC] sigsetjmp/siglongjmp on cygwin
- From: Ben Elliston <bje at redhat dot com>
- Date: Mon, 13 Aug 2001 08:47:41 +1000 (EST)
- Cc: Keith Seitz <keiths at cygnus dot com>, Eli Zaretskii <eliz at is dot elta dot co dot il>, Mark Kettenis <kettenis at science dot uva dot nl>, gdb-patches at sources dot redhat dot com
- References: <Pine.GSO.4.33.0108011357170.26158-100000@makita.cygnus.com><3B738C62.6090607@cygnus.com>
>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
Andrew> Since you know a thing or two about autoconf
Andrew> (http://sources.redhat.com/autobook/ ;-) would you mind giving an
Andrew> opinion on the below.
Andrew> The full thread is at:
Andrew> http://sources.redhat.com/ml/gdb-patches/2001-08/msg00012.html
I can see the arguments from both sides -- localise the warts to
configure.in or push them out into the platform-specific file.
One must keep in mind the traditional approach used by Autoconf for
situations like this: write a test that *detects* whether
sig{set,long}jmp are broken.
The current proposals suffer the problem that GDB and Cygwin versions
will have to follow in lock-step because GDB's configury will assume
that sig{set,long}jmp is either present or absent for Cygwin hosts.
This will not be true once (if?) Cygwin is fixed and there are two
"strains" :-) out there -- those that are fixed and those that are
not.
Ben