public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jsturm@one-point.com
To: gcc-gnats@gcc.gnu.org
Subject: libgcj/2833: New testsuite failures on 3.0 branch
Date: Tue, 15 May 2001 14:16:00 -0000 [thread overview]
Message-ID: <20010515210759.13956.qmail@sourceware.cygnus.com> (raw)
>Number: 2833
>Category: libgcj
>Synopsis: New testsuite failures on 3.0 branch
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue May 15 14:16:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: jsturm@one-point.com
>Release: gcc version 3.0 20010514 (prerelease)
>Organization:
>Environment:
alphapca56-unknown-linux-gnu
>Description:
I have 70+ new testsuite failures on the 3.0 branch since
the EH merge. All of them appear to be dying on a segfault
in _Jv_Throw:
Program received signal SIGSEGV, Segmentation fault.
_ZN4java4lang5Class7isArrayEv (this=0x29a00) at Class.h:175
175 Class.h: No such file or directory.
(gdb) bt
#0 _ZN4java4lang5Class7isArrayEv (this=0x29a00) at Class.h:175
#1 0x200003bae18 in _Z20_Jv_IsAssignableFromPN4java4lang5ClassES2_ (
target=0x29a00, source=0x20000623158)
at ../../../libjava/java/lang/natClass.cc:916
#2 0x200003bb1cc in _Jv_IsInstanceOf (obj=0x12007ffe0, cl=0x29a00)
at ../../../libjava/java/lang/natClass.cc:983
#3 0x2000039b3d8 in __gcj_personality_v0 (version=1, actions=1,
exception_class=5138137972373280321, ue_header=0x12006ffa0,
context=0x3ffffdff2b0) at ../../../libjava/exception.cc:348
#4 0x20000028754 in _Unwind_RaiseException ()
from /home/jsturm/dev/gcc/build/gcc/libgcc_s.so.0
#5 0x2000039a950 in _Jv_Throw (value=0x12007ffe0)
at ../../../libjava/exception.cc:104
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-05-15 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 14:16 jsturm [this message]
2001-06-07 15:14 tromey
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=20010515210759.13956.qmail@sourceware.cygnus.com \
--to=jsturm@one-point.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: 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).