Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
To: cygwin@cygwin.com
From: Adam Irawan <the_sandman@rogers.com>
Subject:  Re: Accessing signal context from a handler
Date: Wed, 26 Oct 2005 21:36:53 +0000 (UTC)
Lines: 26
Message-ID:  <loom.20051026T233204-817@post.gmane.org>
References:  <20020715171545.GC28190@redhat.com> <Pine.GSO.4.44.0207151331220.24745-100000@slinky.cs.nyu.edu>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes

Igor Pechtchanski <pechtcha <at> cs.nyu.edu> writes:
> 
> On Mon, 15 Jul 2002, Christopher Faylor wrote:
> 
> > 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?  [snip]
> >
> > It's not available.
> > cgf
> [snip snip]
> 
> Basically, I'm trying to port an application that intercepts SIGSEGV and
> makes decisions based on the IP of the faulted instruction.  The
> application currently uses the sigaction/ucontext mechanism in Linux.
> Any suggestions on how to do this in Cygwin (preferably similar to the
> Linux code, to maximize reuse) would be appreciated.
> 
> [snipped the code bit]


Wow, dug up an ancient post today that seems to relate to my current problem
more than anything else I've searched for. Just wondering, has there been
changes regarding this topic at all? Thanks alot,
Adam


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