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 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Subject: sigaction siginfo_t & SIGSEGV Date: Tue, 21 Jan 2003 21:00:08 -0500 Message-ID: <83040F98B407E6428FEC18AC720F5D732DB7A1@exchange.tropicnetworks.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Rolf Campbell" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h0M20dZ00785 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 Software Designer Tropic Networks -- 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/