From: Andrew Cagney <ac131313@cygnus.com>
To: bje@cygnus.com
Cc: Keith Seitz <keiths@cygnus.com>,
Eli Zaretskii <eliz@is.elta.co.il>,
Mark Kettenis <kettenis@science.uva.nl>,
gdb-patches@sources.redhat.com
Subject: Re: [RFC] sigsetjmp/siglongjmp on cygwin
Date: Fri, 10 Aug 2001 00:27:00 -0000 [thread overview]
Message-ID: <3B738C62.6090607@cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0108011357170.26158-100000@makita.cygnus.com>
Ben,
Since you know a thing or two about autoconf
( http://sources.redhat.com/autobook/ ;-) would you mind giving an
opinion on the below.
The full thread is at:
http://sources.redhat.com/ml/gdb-patches/2001-08/msg00012.html
Andrew
> 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.
>
> 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.
> Keith
>
> Possible ChangeLog
> 2001-08-01 Keith Seitz <keiths@redhat.com>
>
> * configure.in: Don't use sigsetjmp/siglongjmp on
> cygwin, even if it is available: it doesn't work.
> * configure: Regenerate.
>
> Possible Patch
> Index: configure.in
> ===================================================================
> RCS file: /cvs/src/src/gdb/configure.in,v
> retrieving revision 1.66
> diff -u -p -r1.66 configure.in
> --- configure.in 2001/07/12 13:48:45 1.66
> +++ configure.in 2001/08/01 21:01:29
> @@ -137,11 +137,16 @@ AC_FUNC_ALLOCA
>
> # Check if sigsetjmp is available. Using AC_CHECK_FUNCS won't do
> # since sigsetjmp might only be defined as a macro.
> +# Cygwin has sigsetjmp/siglongjmp, but it doesn't seem to work...
> AC_CACHE_CHECK([for sigsetjmp], gdb_cv_func_sigsetjmp,
> [AC_TRY_COMPILE([
> #include <setjmp.h>
> ], [sigjmp_buf env; while (! sigsetjmp (env, 1)) siglongjmp (env, 1);],
> -gdb_cv_func_sigsetjmp=yes, gdb_cv_func_sigsetjmp=no)])
> +[case "${host}" in
> + *cygwin*) gdb_cv_func_sigsetjmp=no ;;
> + *) gdb_cv_func_sigsetjmp=yes ;;
> +esac
> +], gdb_cv_func_sigsetjmp=no)])
> if test $gdb_cv_func_sigsetjmp = yes; then
> AC_DEFINE(HAVE_SIGSETJMP, 1, [Define if sigsetjmp is available. ])
> fi
>
>
>
>
next prev parent reply other threads:[~2001-08-10 0:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 14:01 Keith Seitz
[not found] ` <s3iae1jjso2.fsf@soliton.wins.uva.nl>
2001-08-01 16:03 ` Keith Seitz
2001-08-01 23:57 ` Eli Zaretskii
2001-08-02 10:25 ` Andrew Cagney
2001-08-02 13:15 ` Mark Kettenis
2001-08-13 14:46 ` Jim Blandy
2001-08-13 15:12 ` Keith Seitz
2001-08-13 15:37 ` Andrew Cagney
2001-08-13 15:43 ` Keith Seitz
2001-08-13 15:52 ` Andrew Cagney
2001-08-13 16:27 ` Keith Seitz
2001-08-13 16:32 ` Christopher Faylor
[not found] ` <20010813222037.A20589@redhat.com>
2001-08-13 19:40 ` [RFC] sigsetjmp/siglongjmp on cygwin -- problem tracked down Andrew Cagney
2001-08-13 19:55 ` Christopher Faylor
2001-08-13 20:10 ` Daniel Jacobowitz
2001-08-13 20:18 ` [RFA] work around sigsetjmp/siglongjmp macro problems Christopher Faylor
2001-08-14 0:06 ` Eli Zaretskii
2001-08-14 7:40 ` Christopher Faylor
2001-08-14 9:34 ` Keith Seitz
2001-08-14 13:01 ` Elena Zannoni
2001-08-14 13:08 ` Christopher Faylor
2001-08-14 23:52 ` Eli Zaretskii
2001-08-14 23:49 ` Eli Zaretskii
2001-08-13 17:11 ` [RFC] sigsetjmp/siglongjmp on cygwin Andrew Cagney
2001-08-13 17:23 ` Keith Seitz
2001-08-03 1:33 ` Eli Zaretskii
2001-08-10 0:16 ` Andrew Cagney
2001-08-01 16:16 ` Andrew Cagney
2001-08-02 13:51 ` Christopher Faylor
2001-08-10 0:27 ` Andrew Cagney [this message]
2001-08-12 15:49 ` Ben Elliston
2001-08-13 2:03 ` Eli Zaretskii
2001-08-13 15:42 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B738C62.6090607@cygnus.com \
--to=ac131313@cygnus.com \
--cc=bje@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@cygnus.com \
--cc=kettenis@science.uva.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox