From: Christopher Faylor <cgf@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] work around sigsetjmp/siglongjmp macro problems
Date: Mon, 13 Aug 2001 20:18:00 -0000 [thread overview]
Message-ID: <20010813231801.A23019@redhat.com> (raw)
In-Reply-To: <20010813201116.A12426@nevyn.them.org>
[NOTE: reply-to set to gdb-patches]
On Mon, Aug 13, 2001 at 08:11:16PM -0700, Daniel Jacobowitz wrote:
>> Doh. Now that you mention it, Cygwin actually already has a mechanism
>> for this. We bump a minor version number when there are api changes,
>> such as this. Then we usually define a macro like
>> "CYGWIN_VERSION_SIGSEJMP_IS_OK" based on the API. It is a little
>> tricky, though, since the actual header file is in newlib not cygwin.
>
>On the other hand, it should be very straightforward to write an
>autoconf test for this. You said that the code in question looked like
>env[36] instead of (env)[36]; just use an argument that would not be
>valid to subscript. env + 1[36], for instance, should generally not
>compile.
Luckily, as Andrew has pointed out, there is no reason to go to this
trouble.
My proposed patch is below. It may even be an obvious fix.
Keith, could you try this out and verify that it fixes the problem?
cgf
2001-08-13 Christopher Faylor <cgf@cygnus.com>
* top.c (SIGSETJMP): Protect macro argument with parentheses.
(SIGLONGJMP): Protect macro argument with parentheses.
Index: top.c
===================================================================
RCS file: /cvs/uberbaum/gdb/top.c,v
retrieving revision 1.42
diff -p -r1.42 top.c
*** top.c 2001/08/01 18:39:23 1.42
--- top.c 2001/08/14 03:05:50
*************** NORETURN void (*error_hook) (void) ATTR_
*** 299,310 ****
directly. */
#if defined(HAVE_SIGSETJMP)
#define SIGJMP_BUF sigjmp_buf
! #define SIGSETJMP(buf) sigsetjmp(buf, 1)
! #define SIGLONGJMP(buf,val) siglongjmp(buf,val)
#else
#define SIGJMP_BUF jmp_buf
#define SIGSETJMP(buf) setjmp(buf)
! #define SIGLONGJMP(buf,val) longjmp(buf,val)
#endif
/* Where to go for return_to_top_level. */
--- 299,310 ----
directly. */
#if defined(HAVE_SIGSETJMP)
#define SIGJMP_BUF sigjmp_buf
! #define SIGSETJMP(buf) sigsetjmp((buf), 1)
! #define SIGLONGJMP(buf,val) siglongjmp((buf), (val))
#else
#define SIGJMP_BUF jmp_buf
#define SIGSETJMP(buf) setjmp(buf)
! #define SIGLONGJMP(buf,val) longjmp((buf), (val))
#endif
/* Where to go for return_to_top_level. */
next prev parent reply other threads:[~2001-08-13 20:18 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 ` [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 ` Christopher Faylor [this message]
2001-08-14 0:06 ` [RFA] work around sigsetjmp/siglongjmp macro problems 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=20010813231801.A23019@redhat.com \
--to=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