From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4725 invoked by alias); 18 May 2003 02:06:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 4702 invoked by uid 71); 18 May 2003 02:06:00 -0000 Date: Sun, 18 May 2003 02:06:00 -0000 Message-ID: <20030518020600.4698.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Andrew Pinski Subject: Re: c++/10840: any way to catch a segmentation fault error? Reply-To: Andrew Pinski X-SW-Source: 2003-05/txt/msg02009.txt.bz2 List-Id: The following reply was made to PR c++/10840; it has been noted by GNATS. From: Andrew Pinski To: snowboy@orgio.net Cc: Andrew Pinski , gcc-gnats@gcc.gnu.org, "Gcc-Bugs@Gcc. Gnu. Org" Subject: Re: c++/10840: any way to catch a segmentation fault error? Date: Sat, 17 May 2003 22:02:31 -0400 No, this is a Microsoft extension, use signal(3) to catch seg faults. Thanks, Andrew Pinski PS Can someone close this bug, as this extension is one which has been discussed before and decided we do not want it.