This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Accessing signal context from a handler
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 26 Oct 2005 17:56:15 -0400
- Subject: Re: Accessing signal context from a handler
- References: <20020715171545.GC28190@redhat.com> <Pine.GSO.4.44.0207151331220.24745-100000@slinky.cs.nyu.edu> <loom.20051026T233204-817@post.gmane.org>
- Reply-to: cygwin at cygwin dot com
On Wed, Oct 26, 2005 at 09:36:53PM +0000, Adam Irawan wrote:
>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,
It's not available.
cgf
--
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/