Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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:	Sun, 1 Feb 2004 10:08:36 -0500 (EST)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	Daniel Diaz <Daniel DOT Diaz AT univ-paris1 DOT fr>
cc:	cygwin AT cygwin DOT com
Subject:	Re: cygwin and SIGSEGV addr
In-Reply-To:	<200402011051.i11Apq113492@asterix.univ-paris1.fr>
Message-ID:	<Pine.GSO.4.56.0402010958570.20927@slinky.cs.nyu.edu>
References:	<200402011051 DOT i11Apq113492 AT asterix DOT univ-paris1 DOT fr>
MIME-Version:	1.0

On Sun, 1 Feb 2004, Daniel Diaz wrote:

> Hi
>
> I'm the author of GNU Prolog and to improve my cygwin port I need to be
> able to obtain the address that caused a SIGSEGV when I trap it inside a
> handler. I cannot find any documentation on this. Could you help me
> please ?
>
> Thank you for your attention.
>      Daniel Diaz

Daniel,

It is better to address questions of this sort to the official Cygwin
mailing list (see <http://cygwin.com/lists.html#available-lists>).  Not
only are you going to get access to more expertise than any one person can
provide, but your question (and the others' answers)  will be stored in
the (searchable) list archives for people to find later. I'm redirecting
this query to the appropriate cygwin mailing list, and setting the
Reply-To: accordingly.

To answer your question, you seem to be asking about SA_SIGINFO-style
contexts.  These aren't implemented in Cygwin (yet), but CGF (one of the
core maintainers of Cygwin) has mentioned that with some of his upcoming
changes, SA_SIGINFO support will be available.  You might want to watch
the CVS commits to see when this happens, and then either wait for a
snapshot or build your own DLL.  Note that once you do this, your
newly-built executable will have a versioned dependence, so you won't be
able to release it to people until the next official Cygwin release after
the necessary changes.

Alternatively, there were a couple of recipes posted on how to obtain this
information via the Win32 system calls.  Searching Google for "SA_SIGINFO
site:cygwin.com" should point you to those discussions.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -