public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/45693]  New: [4.6 regression] All Tru64 UNIX EH tests fail
Date: Thu, 16 Sep 2010 19:10:00 -0000	[thread overview]
Message-ID: <bug-45693-279@http.gcc.gnu.org/bugzilla/> (raw)

Between 20100607 and 20100624, all Tru64 UNIX V5.1B EH tests started to fail,
e.g.

FAIL: g++.old-deja/g++.mike/eh33.C execution test

This testcase segfaults like this:

Program received signal SIGSEGV, Segmentation fault.
__cxa_call_unexpected (exc_obj_in=0x70)
    at /vol/gcc/src/hg/trunk/local/libstdc++-v3/libsupc++/unwind-cxx.h:374
374       return (c & 1);
(gdb) where
#0  __cxa_call_unexpected (exc_obj_in=0x70)
    at /vol/gcc/src/hg/trunk/local/libstdc++-v3/libsupc++/unwind-cxx.h:374
#1  0x0000000120001a40 in foo ()
    at
/vol/gcc/src/hg/trunk/local/gcc/testsuite/g++.old-deja/g++.mike/eh33.C:10
#2  0x0000000120001a80 in main ()
    at
/vol/gcc/src/hg/trunk/local/gcc/testsuite/g++.old-deja/g++.mike/eh33.C:15

I'll start a reghunt to identify the culprit patch.

  Rainer


-- 
           Summary: [4.6 regression] All Tru64 UNIX EH tests fail
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ro at gcc dot gnu dot org
 GCC build triplet: alpha-dec-osf5.1b
  GCC host triplet: alpha-dec-osf5.1b
GCC target triplet: alpha-dec-osf5.1b


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45693


             reply	other threads:[~2010-09-16 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 19:10 ro at gcc dot gnu dot org [this message]
2010-09-17  9:45 ` [Bug target/45693] " rguenth at gcc dot gnu dot org

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=bug-45693-279@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).