Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 15 Jul 2002 13:15:45 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Accessing signal context from a handler Message-ID: <20020715171545.GC28190@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i 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? Accessing the Windows CONTEXT >object should do. I've looked through winsup/cygwin/exceptions.cc, and >that info doesn't seem to be saved anywhere for later access, nor is it >passed into the handler. It's not available. cgf -- Please do not send me personal email with cygwin questions. Use the resources at http://cygwin.com/ . -- 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/