This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: sigaction siginfo_t & SIGSEGV
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Rolf Campbell <rcampbell at tropicnetworks dot com>
- Cc: cygwin at cygwin dot com
- Date: Tue, 21 Jan 2003 23:27:09 -0500 (EST)
- Subject: Re: sigaction siginfo_t & SIGSEGV
- Reply-to: cygwin at cygwin dot com
On Tue, 21 Jan 2003, Rolf Campbell wrote:
> I'm trying to write an application that can run some code when a certain
> memory address is read or written.
> My first theory was to use mprotect to remove read/write permissions
> from a section and then catch SIGSEGV, but siginfo_t doesn't seem to be
> defined.
> Is hooking a signal using the 'sa_sigaction' member of 'struct
> sigaction' supported in CygWin?
>
> I noticed that struct siginfo_t is declared in sys/signal.h, but inside
> a couple of #ifdef:
> #if defined(__rtems__)
> #if defined(_POSIX_REALTIME_SIGNALS)
>
> And it doesn't have the member that I need anyways (si_addr).
>
> Does anyone know of any other ways of trapping reads/writes to/from
> memory regions?
>
> -Rolf Campbell
No, sigaction is not supported on Cygwin. It's on the TODO list.
There has been some discussion on how to set up your own signal handler on
this list last October. See <http://cygwin.com/ml/cygwin/2002-10/msg00236.html>.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
-- /usr/games/fortune
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/