public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/59415] New: ICE segfault in verify_bb_vtables for g++ -S -fvtable-verify=std -fsanitize=null Date: Sat, 07 Dec 2013 00:17:00 -0000 [thread overview] Message-ID: <bug-59415-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59415 Bug ID: 59415 Summary: ICE segfault in verify_bb_vtables for g++ -S -fvtable-verify=std -fsanitize=null Product: gcc Version: 4.9.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: cmtice at google dot com, dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, mpolacek at gcc dot gnu.org Created attachment 31395 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31395&action=edit test.ii / compiled with g++ -fvtable-verify=std -fsanitize=null $ g++ -S -fvtable-verify=std -fsanitize=null test.ii fails for the attached file on x86-64-gnu-linux with: test.ii: In member function '_CharT* basic_string<_CharT, _Traits, _Alloc>::_M_data() const [with _CharT = char; _Traits = char_traits<char>; _Alloc = allocator<char>]': test.ii:34:11: internal compiler error: Segmentation fault _CharT* _M_data() const { ^ 0xbafabf crash_signal ../../gcc/toplev.c:336 0xe19e37 verify_bb_vtables ../../gcc/vtable-verify.c:592 0xe19e37 vtable_verify_main() ../../gcc/vtable-verify.c:750
next reply other threads:[~2013-12-07 0:17 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-07 0:17 burnus at gcc dot gnu.org [this message] 2013-12-07 0:55 ` [Bug sanitizer/59415] " burnus at gcc dot gnu.org 2013-12-08 18:31 ` mpolacek at gcc dot gnu.org 2013-12-09 12:44 ` mpolacek at gcc dot gnu.org 2013-12-09 14:44 ` mpolacek at gcc dot gnu.org 2013-12-09 14:45 ` mpolacek at gcc dot gnu.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-59415-4@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: 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).