Re: Accessing signal context from a handler
On Wed, Oct 26, 2005 at 05:56:15PM -0400, Christopher Faylor wrote: > On Wed, Oct 26, 2005 at 09:36:53PM +, 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 You left out the bit where ucontext used to not be passed at all, but in current snapshots it's passed as a null pointer... -- 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/
Re: Accessing signal context from a handler
On Wed, Oct 26, 2005 at 09:36:53PM +, 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/
Re: Accessing signal context from a handler
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/
