public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/22284] [4.1 Regression] ia64 exception handling broken Date: Fri, 22 Jul 2005 06:25:00 -0000 [thread overview] Message-ID: <20050722055121.9546.qmail@sourceware.org> (raw) In-Reply-To: <20050703113441.22284.jsm28@gcc.gnu.org> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1448 bytes --] ------- Additional Comments From hjl at lucon dot org 2005-07-22 05:51 ------- It looks like the unwind info in libstdc++.so is bad. (gdb) r Starting program: /export/build/gnu/gcc-next/build-ia64-linux/gcc/testsuite/cond1.exe Program received signal SIGSEGV, Segmentation fault. 0x20000000001b9b90 in read_encoded_value_with_base (encoding=180 '´', base=0, p=0x40000000000021b0 "\002", val=0x60000fffffffa5d0) at unwind-pe.h:267 267 result = *(_Unwind_Internal_Ptr *) result; Current language: auto; currently c++ (gdb) p result $1 = 232 (gdb) bt #0 0x20000000001b9b90 in read_encoded_value_with_base (encoding=180 '´', base=0, p=0x40000000000021b0 "\002", val=0x60000fffffffa5d0) at unwind-pe.h:267 #1 0x20000000001ba2e0 in get_ttype_entry (info=0x60000fffffffa608, i=Variable "i" is not available. ) at /net/gnu-3/export/gnu/src/gcc-next/gcc/libstdc++-v3/libsupc++/eh_personality.cc:209 #2 0x20000000001babb0 in __gxx_personality_v0 (version=Variable "version" is not available. ) at /net/gnu-3/export/gnu/src/gcc-next/gcc/libstdc++-v3/libsupc++/eh_personality.cc:550 #3 0x20000000002ec590 in _Unwind_RaiseException () from /lib/libgcc_s.so.1 #4 0x20000000001bb420 in __cxa_throw (obj=Variable "obj" is not available. ) at /net/gnu-3/export/gnu/src/gcc-next/gcc/libstdc++-v3/libsupc++/eh_throw.cc:72 #5 0x4000000000000d00 in main () -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22284
next prev parent reply other threads:[~2005-07-22 5:51 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-03 11:34 [Bug c++/22284] New: [4.1 Regression] Many C++ testsuite failures jsm28 at gcc dot gnu dot org 2005-07-03 11:37 ` [Bug c++/22284] " pinskia at gcc dot gnu dot org 2005-07-03 11:38 ` pinskia at gcc dot gnu dot org 2005-07-03 12:09 ` jakub at redhat dot com 2005-07-03 12:17 ` joseph at codesourcery dot com 2005-07-03 13:40 ` jakub at redhat dot com 2005-07-03 13:54 ` joseph at codesourcery dot com 2005-07-03 18:24 ` danglin at gcc dot gnu dot org 2005-07-04 10:47 ` jsm28 at gcc dot gnu dot org 2005-07-06 21:29 ` [Bug c++/22284] [4.1 Regression] sjlj exception handling broken rth at gcc dot gnu dot org 2005-07-06 21:39 ` rearnsha at gcc dot gnu dot org 2005-07-07 22:49 ` [Bug middle-end/22284] " jsm28 at gcc dot gnu dot org 2005-07-16 21:31 ` [Bug middle-end/22284] [4.1 Regression] ia64 " pinskia at gcc dot gnu dot org 2005-07-22 5:46 ` hjl at lucon dot org 2005-07-22 6:25 ` hjl at lucon dot org [this message] 2005-07-22 17:26 ` [Bug libstdc++/22284] " hjl at lucon dot org 2005-07-22 17:59 ` pinskia at gcc dot gnu dot org 2005-07-25 15:14 ` sje at cup dot hp dot com 2005-07-29 13:40 ` cvs-commit at gcc dot gnu dot org 2005-07-29 13:58 ` pinskia 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=20050722055121.9546.qmail@sourceware.org \ --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: 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).