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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Tue, 21 Jan 2003 23:27:09 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Rolf Campbell cc: cygwin AT cygwin DOT com Subject: Re: sigaction siginfo_t & SIGSEGV In-Reply-To: <83040F98B407E6428FEC18AC720F5D732DB7A1@exchange.tropicnetworks.com> Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 . Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT 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/