From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eli Zaretskii" To: bje@redhat.com Cc: ac131313@cygnus.com, keiths@cygnus.com, kettenis@science.uva.nl, gdb-patches@sources.redhat.com Subject: Re: [RFC] sigsetjmp/siglongjmp on cygwin Date: Mon, 13 Aug 2001 02:03:00 -0000 Message-id: <2593-Mon13Aug2001120249+0300-eliz@is.elta.co.il> References: <3B738C62.6090607@cygnus.com> <15223.1933.710748.364749@scooby.brisbane.redhat.com> X-SW-Source: 2001-08/msg00135.html > From: Ben Elliston > Date: Mon, 13 Aug 2001 08:47:41 +1000 (EST) > > The current proposals suffer the problem that GDB and Cygwin versions > will have to follow in lock-step because GDB's configury will assume > that sig{set,long}jmp is either present or absent for Cygwin hosts. > This will not be true once (if?) Cygwin is fixed and there are two > "strains" :-) out there -- those that are fixed and those that are > not. I suggested to put the work-around into config.site, precisely to solve this. Assuming such a config.site is made part of the core Cygwin distribution, whenever sigsetjmp starts working, config.site should be updated. So a user which upgrades to a newer version of Cygwin has this issue magically taken care of during the upgrade.