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 Date: Wed, 26 Oct 2005 17:56:15 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Accessing signal context from a handler Message-ID: <20051026215615.GA15549@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20020715171545 DOT GC28190 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Wed, Oct 26, 2005 at 09:36:53PM +0000, Adam Irawan wrote: >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, 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/