public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/44817] New: Stage2/stage3 genautomata has invalid memory access Date: Sun, 04 Jul 2010 23:39:00 -0000 [thread overview] Message-ID: <bug-44817-682@http.gcc.gnu.org/bugzilla/> (raw) On Linux/x86-64, revision 161806 gave: # /usr/bin/valgrind --tool=memcheck build/genautomata /export/gnu/import/svn/gcc-test/src-trunk/gcc/config/i386/i386.md insn-conditions.md > /dev/null ==5903== Memcheck, a memory error detector ==5903== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==5903== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info ==5903== Command: build/genautomata /export/gnu/import/svn/gcc-test/src-trunk/gcc/config/i386/i386.md insn-conditions.md ==5903== ==5903== Invalid read of size 8 ==5903== at 0x401BE7: check_absence_pattern_sets (genautomata.c:4353) ==5903== by 0x40D85F: create_automata (genautomata.c:3503) ==5903== by 0x4101D5: expand_automata (genautomata.c:9093) ==5903== by 0x4115B8: main (genautomata.c:9543) ==5903== Address 0x1c is not stack'd, malloc'd or (recently) free'd ==5903== ==5903== ==5903== Process terminating with default action of signal 11 (SIGSEGV) ==5903== Access not within mapped region at address 0x1C ==5903== at 0x401BE7: check_absence_pattern_sets (genautomata.c:4353) ==5903== by 0x40D85F: create_automata (genautomata.c:3503) ==5903== by 0x4101D5: expand_automata (genautomata.c:9093) ==5903== by 0x4115B8: main (genautomata.c:9543) ==5903== If you believe this happened as a result of a stack ==5903== overflow in your program's main thread (unlikely but ==5903== possible), you can try to increase the size of the ==5903== main thread stack using the --main-stacksize= flag. ==5903== The main thread stack size used in this run was 8388608. ==5903== ==5903== HEAP SUMMARY: ==5903== in use at exit: 11,187,082 bytes in 73,185 blocks ==5903== total heap usage: 83,419 allocs, 10,234 frees, 32,694,074 bytes allocated ==5903== -- Summary: Stage2/stage3 genautomata has invalid memory access Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl dot tools at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44817
next reply other threads:[~2010-07-04 23:39 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-04 23:39 hjl dot tools at gmail dot com [this message] 2010-07-05 0:06 ` [Bug middle-end/44817] " hjl dot tools at gmail dot com 2010-07-05 0:20 ` hjl dot tools at gmail dot com 2010-07-05 14:09 ` ubizjak at gmail dot com 2010-07-05 15:57 ` hjl dot tools at gmail dot com 2010-07-26 18:41 ` hjl dot tools at gmail dot com
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-44817-682@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).