From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Faylor To: gdb-patches@sources.redhat.com Subject: Re: [RFC] sigsetjmp/siglongjmp on cygwin Date: Thu, 02 Aug 2001 13:51:00 -0000 Message-id: <20010802165111.A31849@redhat.com> References: <3B688DDB.5080102@cygnus.com> X-SW-Source: 2001-08/msg00054.html On Wed, Aug 01, 2001 at 07:16:43PM -0400, Andrew Cagney wrote: > >> Can't say I like your patch. An alternative would be to #undef >> HAVE_SIGSETJMP in the cygwin xm.h file. That isolates this bogosity >> nicely in a platform-specific file. Perhaps some other folks have an >> opinion on this. If you don't hear anything, feel free to choose a >> hack. > > >I'm not so warm on the idea of putting something in an xm.h file. I >think the *SETJMP test, hacks, warts, and all should be localized. How can we test for sigsetjmp working or not working in a cross-build environment, though. I have changed opinions on whether sigsetjmp should work in cygwin about five times today. After spending some time looking at the code, I have to confess that it seems like it should work ok to me. That's my current opinion, anyway. I'd like to understand the kind of problems that Keith is seeing. Maybe there is something that can be done to the sigsetjmp/siglongjmp macros to fix this problem in gdb so that we don't have to say "upgrade cygwin". I'm very interested in fixing cygwin, though, of course. cgf