public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: chmouel@mandrakesoft.com To: gcc-gnats@gcc.gnu.org Cc: future@mandrakesoft.com Subject: c++/2447: g++ don't handle execption when using with -fomit-frame-pointer Date: Sat, 31 Mar 2001 17:26:00 -0000 [thread overview] Message-ID: <20010401012329.3559.qmail@sourceware.cygnus.com> (raw) >Number: 2447 >Category: c++ >Synopsis: g++ don't handle execption when using with -fomit-frame-pointer >Confidential: no >Severity: serious >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sat Mar 31 17:26:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: g++ >Release: 3.1 20010331 >Organization: >Environment: i686-pc-linux >Description: When compiling the attached code with fomi-frame-pointer it does segfault when it should catch the error : [t.cc is the example file] [gc@bi ~/tmp] g++ t.cc [gc@bi ~/tmp] ./a.out step #1 step #2 step #3 catched! [gc@bi ~/tmp] g++ -fomit-frame-pointer t.cc [gc@bi ~/tmp] ./a.out step #1 step #2 step #3 Aborted (core dumped) [gc@bi ~/tmp] >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="t.cc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="t.cc" I2luY2x1ZGUgPGlvc3RyZWFtPgoKc3RydWN0IFBTTUVPRiB7fQo7CgoKdm9pZCBzZWNvbmRfbGV2 ZWwodm9pZCkgewogIGNvdXQgPDwgInN0ZXAgIzMiIDw8IGVuZGw7CiAgdGhyb3cgUFNNRU9GKCk7 CiAgY291dCA8PCAic3RlcCAjNCIgPDwgZW5kbDsKfQoKdm9pZCBmaXJzdF9sZXZlbCh2b2lkKSB7 CiAgdHJ5IHsKICAgIGNvdXQgPDwgInN0ZXAgIzEiIDw8IGVuZGw7CiAgICAvL3Rocm93IFBTTUVP RigpOwogICAgY291dCA8PCAic3RlcCAjMiIgPDwgZW5kbDsKICAgIHNlY29uZF9sZXZlbCgpOwog IH0KICBjYXRjaCAoUFNNRU9GKSB7CiAgICBjb3V0IDw8ICJjYXRjaGVkISIgPDwgZW5kbDsKICB9 Cn0KCgppbnQgbWFpbihpbnQgYXJnYywgY2hhciAqYXJndltdKQp7CiAgZmlyc3RfbGV2ZWwoKTsK ICByZXR1cm4gMDsKCn0K
next reply other threads:[~2001-03-31 17:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-03-31 17:26 chmouel [this message] 2002-02-20 10:56 jason 2002-03-03 11:46 Craig Rodrigues 2002-03-19 6:16 Jason Merrill 2002-11-29 12:51 bangerth
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=20010401012329.3559.qmail@sourceware.cygnus.com \ --to=chmouel@mandrakesoft.com \ --cc=future@mandrakesoft.com \ --cc=gcc-gnats@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: linkBe 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).