Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Mon, 15 Jul 2002 13:15:45 -0400
From:	Christopher Faylor <cgf-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Accessing signal context from a handler
Message-ID:	<20020715171545.GC28190@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<Pine DOT GSO DOT 4 DOT 44 DOT 0207151240150 DOT 24745-100000 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version:	1.0
In-Reply-To:	<Pine.GSO.4.44.0207151240150.24745-100000@slinky.cs.nyu.edu>
User-Agent:	Mutt/1.3.23.1i

On Mon, Jul 15, 2002 at 01:00:23PM -0400, Igor Pechtchanski wrote:
>Does Cygwin allow accessing the context (register state, etc) of the
>faulted instruction from a signal handler installed by sigaction(),
>similar to ucontext/mcontext in Linux?  Accessing the Windows CONTEXT
>object should do.  I've looked through winsup/cygwin/exceptions.cc, and
>that info doesn't seem to be saved anywhere for later access, nor is it
>passed into the handler.

It's not available.

cgf
--
Please do not send me personal email with cygwin questions.
Use the resources at http://cygwin.com/ .

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -