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 To: cygwin AT cygwin DOT com From: Adam Irawan Subject: Re: Accessing signal context from a handler Date: Wed, 26 Oct 2005 21:36:53 +0000 (UTC) Lines: 26 Message-ID: References: <20020715171545 DOT GC28190 AT redhat DOT com> 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 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/