public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: topiolli@ee.oulu.fi
To: gcc-gnats@gcc.gnu.org
Subject: c++/4381: Exceptions virtually inherited from a class cause segmentation fault at run time
Date: Mon, 24 Sep 2001 02:46:00 -0000	[thread overview]
Message-ID: <20010924094453.25922.qmail@sourceware.cygnus.com> (raw)

>Number:         4381
>Category:       c++
>Synopsis:       Exceptions virtually inherited from a class cause segmentation fault at run time
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Sep 24 02:46:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     topiolli@ee.oulu.fi
>Release:        g++ 3.0.1
>Organization:
>Environment:
SunOS 5.8 Generic_108528-09 sun4u sparc SUNW,Ultra-80

Reading specs from /local/bin/../lib/gcc-lib/sparc-sun-solaris2.8/3.0.1/specs
Configured with: ../configure --with-cpu=ultrasparc
Thread model: posix
gcc version 3.0.1
>Description:
If an exception is virtually inherited from a base class, it
causes a segmentation fault when thrown at run time. The
problem occurs only when a throw clause is specified in
a function description. The exception that is specified 
first in the clause will work fine, the rest not.

There are also some other problems with virtually inherited
exceptions, but I haven't been able to track them down this
far. One of them occurs with long try blocks. I get an error
message from the assembler which says "constant value out
of range".
>How-To-Repeat:
Compile the attached program with g++ -o test Test3.cc and
run it. It should cause a segmentation fault.
>Fix:
N/A
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="Test3.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Test3.cc"

I2luY2x1ZGUgPHN0cmluZz4KI2luY2x1ZGUgPGlvc3RyZWFtPgoKdXNpbmcgbmFtZXNwYWNlIHN0
ZDsKCmNsYXNzIEJhc2Uge307CgpjbGFzcyBBIDogdmlydHVhbCBwdWJsaWMgQmFzZQp7CnB1Ymxp
YzoKCUEoaW50IGZvbykge30KfTsKCmNsYXNzIEIgOiB2aXJ0dWFsIHB1YmxpYyBCYXNlCnsKcHVi
bGljOgoJQihpbnQgZm9vKSB7fQp9OwoKCnZvaWQgZnVuYygpIHRocm93IChCJixBJikgLy9yZW1v
dmUgdGhyb3cgY2xhdXNlIGFuZCBpdCB3aWxsIHdvcmsKewoJdGhyb3cgQSgxKTsgLy9jYXVzZXMg
YSBzZWdtZW50YXRpb24gZmF1bHQKCS8vdGhyb3cgQigxKTsgLy93b3JrcwoJLy9Cb3RoIHdvcmsg
aWYgdGhleSBhcmUgbm90IF92aXJ0dWFsbHlfIGluaGVyaXRlZCBmcm9tIEJhc2UKfQoKaW50IG1h
aW4odm9pZCkKewoJdHJ5CXsJZnVuYygpOyB9CgljYXRjaCAoQSYgYSkgeyBjZXJyIDw8ICJBIiA8
PCBlbmRsOyB9CgljYXRjaCAoQiYgYSkgeyBjZXJyIDw8ICJCIiA8PCBlbmRsOyB9Cn0K


             reply	other threads:[~2001-09-24  2:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-24  2:46 topiolli [this message]
2001-09-27 22:27 rodrigc
2002-03-17  9:28 jason
2002-03-17 16:15 jason

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=20010924094453.25922.qmail@sourceware.cygnus.com \
    --to=topiolli@ee.oulu.fi \
    --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).