public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: starling@location.invalid
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/10266: throw crashes with SIGABRT, no matter what.
Date: Sun, 30 Mar 2003 00:13:00 -0000	[thread overview]
Message-ID: <20030329210300.32700.qmail@sources.redhat.com> (raw)


>Number:         10266
>Category:       libstdc++
>Synopsis:       throw crashes with SIGABRT, no matter what.
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Mar 29 21:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Starling
>Release:        libstdc++-v3 (5.0.2 I think...)
>Organization:
>Environment:

>Description:
The synopsis says it all.  I'm not experienced enough to discern much more.  _Unwind_RaiseException always returns _URC_END_OF_STACK even when there is a catch handler.  That's as far as I could get.
>How-To-Repeat:
$ g++ trythrow.cpp
$ ./a.out
Aborted (core dumped)
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="trythrow.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="trythrow.cpp"

I2luY2x1ZGUgPHN0cmluZz4KI2luY2x1ZGUgPGlvc3RyZWFtPgoKdXNpbmcgc3RkOjpjb3V0Owp1
c2luZyBzdGQ6OmNlcnI7CnVzaW5nIHN0ZDo6ZW5kbDsKdXNpbmcgc3RkOjpzdHJpbmc7CgovL0Eg
c2ltcGxlIGNsYXNzIHdlIHdhbnQgdG8gdGhyb3cKc3RydWN0IEVycm9yIHsKCXN0cmluZyBkYXRh
OwoJRXJyb3IoY29uc3QgY2hhciogbXNnKSA6IGRhdGEobXNnKSB7fQp9OwoKLy9JZiB5b3UgZGVm
aW5lIE1BS0VJVFdPUkssIFNJR0FCUlQgaXMgcmVwbGFjZWQgYnkgYSB1c2VyIAovL2hhbmRsZXIg
dGhhdCBkb2Vzbid0IGR1bXAgY29yZS4uLiBidXQgc28gd2hhdD8KLy8jZGVmaW5lIE1BS0VJVFdP
UksKCiNpZmRlZiBNQUtFSVRXT1JLCiNpbmNsdWRlIDxzaWduYWwuaD4KCnZvaWQgZG9ub3RoaW5n
KGludCBzaWduYWwpIHsKCS8qIEhpLiovCglleGl0KDApOwp9CgojZW5kaWYKCmludCBtYWluKHZv
aWQpIHsKCiNpZmRlZiBNQUtFSVRXT1JLCglzaWduYWwoU0lHQUJSVCwgZG9ub3RoaW5nKTsKI2Vu
ZGlmCgovKioqKioqKioqKioqKioqICBNYWluIENvZGUgU2VjdGlvbiAqKioqKioqKioqKioqKioq
Ki8KCgl0cnkgewoKCQl0aHJvdyBFcnJvcigiVGhpcyB3aWxsIGNhdXNlIGEgU0lHQUJSVCIpOwoK
CX0gY2F0Y2goRXJyb3IgbXNnKSB7CgkJY2VyciA8PCBtc2cuZGF0YSA8PCBlbmRsOwoJfSBjYXRj
aChjb25zdCBFcnJvciYgbXNnKSB7CgkJY2VyciA8PCBtc2cuZGF0YSA8PCBlbmRsOwoJfSBjYXRj
aCguLi4pIHsKCQljZXJyIDw8ICJJIGhhdmUgbm8gaWRlYSEiIDw8IGVuZGw7Cgl9CgoJY291dCA8
PCAiUXVpdHRpbmcuLi4iIDw8IGVuZGw7CgoJcmV0dXJuIDA7Cn0K


             reply	other threads:[~2003-03-29 21:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-30  0:13 starling [this message]
2003-03-30 17:45 ehrhardt
2003-03-30 18:02 ehrhardt

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=20030329210300.32700.qmail@sources.redhat.com \
    --to=starling@location.invalid \
    --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: 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).