Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Mon, 16 Jun 2003 19:20:41 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: "Hirsch, Matthew" cc: cygwin AT cygwin DOT com Subject: Re: Porting Sun's XView to Cygwin: ucontext.h/sigcontext workaround? In-Reply-To: <72D0ADEAED839645B61AF697B3ACB0DC9E67A3@peaexch3.analogic.com> Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 16 Jun 2003, Hirsch, Matthew wrote: > Hi list. > > I'm working on porting Sun Microsystems's antiquated XView libraries to > Cygwin. The only major hangup I've run into is the absence of the signal > context functionality (ucontext.h and sigcontext). I've read through the > archives of this distribution, and I know this has been discussed at some > length, especially by Igor Pechtchanski, but no resolution was reached. > > Has anyone found a suitable workaround? > > Thanks much.. > Matt Hirsch Matt, Unfortunately, the best solution at this point is the one outlined in (the bug Allen mentioned has been fixed, so my original proposal of using cygwin_internal should also work). You should then be able to use GetThreadContext to retrieve the context. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/