From: Andrew Cagney <ac131313@cygnus.com>
To: Christopher Faylor <cgf@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] sigsetjmp/siglongjmp on cygwin -- problem tracked down
Date: Mon, 13 Aug 2001 19:40:00 -0000 [thread overview]
Message-ID: <3B788F78.8050005@cygnus.com> (raw)
In-Reply-To: <20010813222037.A20589@redhat.com>
> So, with the above buggy code, we'll eventually derefernce *catch_return[36]
> when we should be dereferencing (*catch_return)[36].
>
> I'll fix cygwin. How do we want to fix gdb?
>
> I could add a define in setjmp.h like this:
>
> #define WORKING_SETJMP 1
The BSD way of doing it was:
#include <sys/param.h>
#if BSD >= 199506
... was this from the last bsd release ever ...
#endf
While it leads to pretty obscure tests (like the above) it did make it
possible to test for anything constrained to a specific release.
It may be easier to just tweek GDB so that:
(NORETURN void) SIGLONGJMP (*catch_return, (int) reason);
is written more robustly as:
SIGLONGJMP ((*catch_return), ((int) reason));
If CYGWIN has this bug, chance has it that some other OS will as well.
Hmm, Macro's are (er never mind :-).
Andrew
next prev parent reply other threads:[~2001-08-13 19:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 14:01 [RFC] sigsetjmp/siglongjmp on cygwin 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 ` Andrew Cagney [this message]
2001-08-13 19:55 ` [RFC] sigsetjmp/siglongjmp on cygwin -- problem tracked down 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
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=3B788F78.8050005@cygnus.com \
--to=ac131313@cygnus.com \
--cc=cgf@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/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