This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug preprocessor/50144] cc1plus double free / out of bounds read
- From: "edwintorok at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 21 Aug 2011 16:41:19 +0000
- Subject: [Bug preprocessor/50144] cc1plus double free / out of bounds read
- Auto-submitted: auto-generated
- References: <bug-50144-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50144
--- Comment #3 from TÃrÃk Edwin <edwintorok at gmail dot com> 2011-08-21 16:41:19 UTC ---
(In reply to comment #2)
> The valgrind errors about search_line_sse2 are valgrind bugs rather than gcc
> bugs. Just ignore them.
OK, I'll try to find some other valgrind trace.
(In reply to comment #0)
> CXX MemoryBuiltins.lo
> *** glibc detected ***
> /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6.1/cc1plus: double free or
> corruption (out): 0x0000000002a0e280 ***
> ======= Backtrace: =========
> /lib/x86_64-linux-gnu/libc.so.6[0x3c71472606]
> /lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x3c7147733c]
> /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6.1/cc1plus(ggc_internal_alloc_stat+0x25e)[0x5bb86e]
> /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6.1/cc1plus(ggc_internal_cleared_alloc_stat+0x16)[0x6c1446]
> /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6.1/cc1plus(make_node_stat+0x1f)[0x8e1fff]
> /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6.1/cc1plus(alloc_stmt_list+0x5a)[0x8059ca]
> /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6.1/cc1plus(push_stmt_list+0x6)[0x5b47f6]
> /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6.1/cc1plus[0x550e25]
> /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6.1/cc1plus(begin_if_stmt+0x15)[0x551765]
begin_if_stmt appears to be part of the parser though, not the preprocessor
(I thought if refers to #if, but apparently not). So was this a parser crash?