public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10840: any way to catch a segmentation fault error?
Date: Sun, 18 May 2003 02:06:00 -0000	[thread overview]
Message-ID: <20030518020600.4698.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/10840; it has been noted by GNATS.

From: Andrew Pinski <pinskia@physics.uc.edu>
To: snowboy@orgio.net
Cc: Andrew Pinski <pinskia@physics.uc.edu>, gcc-gnats@gcc.gnu.org,
   "Gcc-Bugs@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.
 


             reply	other threads:[~2003-05-18  2:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18  2:06 Andrew Pinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-18  2:41 bangerth
2003-05-18  1:56 snowboy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030518020600.4698.qmail@sources.redhat.com \
    --to=pinskia@physics.uc.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).