From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,11a62e323672426b,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-05-12 02:29:10 PST
Path: archiver1.google.com!postnews1.google.com!not-for-mail
From: okellogg@freenet.de (Oliver Kellogg)
Newsgroups: comp.lang.ada
Subject: GNAT bending signal handlers
Date: 12 May 2003 02:29:10 -0700
Organization: http://groups.google.com/
Message-ID: <6a6390b8.0305120129.24683c2b@posting.google.com>
NNTP-Posting-Host: 53.122.197.194
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1052731750 31318 127.0.0.1 (12 May 2003 09:29:10
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 12 May 2003 09:29:10 GMT
Xref: archiver1.google.com comp.lang.ada:37230
Date: 2003-05-12T09:29:10+00:00
List-Id: <comp.lang.ada>

What is the reason that GNAT changes the SIGSEGV handler?

We would really like to get a core file.

(Similar for other signals: We'd like to get the Unix default
behavior where applicable.)

Thanks,

Oliver Kellogg