From: Keith Seitz <keiths@cygnus.com>
To: <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] work around sigsetjmp/siglongjmp macro problems
Date: Tue, 14 Aug 2001 09:34:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0108140934230.23443-100000@makita.cygnus.com> (raw)
In-Reply-To: <20010813231801.A23019@redhat.com>
On Mon, 13 Aug 2001, Christopher Faylor wrote:
> 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?
Yep, works just fine.
Keith
> 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-14 9:34 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 ` [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 [this message]
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=Pine.GSO.4.33.0108140934230.23443-100000@makita.cygnus.com \
--to=keiths@cygnus.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