From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: bje@redhat.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 15:42:00 -0000
Message-id: <3B7857A8.3040708@cygnus.com>
References: <Pine.GSO.4.33.0108011357170.26158-100000@makita.cygnus.com> <3B738C62.6090607@cygnus.com> <15223.1933.710748.364749@scooby.brisbane.redhat.com> <2593-Mon13Aug2001120249+0300-eliz@is.elta.co.il>
X-SW-Source: 2001-08/msg00149.html

> 
> 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.


Eli, can you expand a little.  I'm not sure what would happen if a 
current GDB was configured/built on an old cygwin which didn't have the 
config.site file.

	Andrew