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, 22 Jan 2003 10:40:20 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: sigaction siginfo_t & SIGSEGV Message-ID: <20030122154020.GD4903@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <83040F98B407E6428FEC18AC720F5D732DB7A1 AT exchange DOT tropicnetworks DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i On Tue, Jan 21, 2003 at 11:27:09PM -0500, Igor Pechtchanski wrote: >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. That's overstating the situation. sigaction() is certainly supported in cygwin. The sa_sigaction field in the sigaction struct is not. cgf -- 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/