Bug 10331 - *** Error in `/opt/ccache/bin/g++': free(): invalid next size (normal): 0x0000000001b2bf40 ***
Summary: *** Error in `/opt/ccache/bin/g++': free(): invalid next size (normal): 0x000...
Status: NEEDINFO
Alias: None
Product: ccache
Classification: Unclassified
Component: ccache (show other bugs)
Version: 3.1.9
Hardware: All All
: P5 normal
Target Milestone: ---
Assignee: Joel Rosdahl
QA Contact: Joel Rosdahl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-17 14:24 UTC by Eric Chamberland
Modified: 2014-01-08 18:50 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Chamberland 2013-12-17 14:24:34 UTC
Hi,

while compiling I got the following error:

*** Error in `/opt/ccache/bin/g++': free(): invalid next size (normal): 0x0000000001b2bf40 ***

here are some informations:

 ccache --s
cache directory                     /pmi/cmpbib/.ccache/
cache hit (direct)               1585898
cache hit (preprocessed)          269624
cache miss                        215394
called for link                   297770
compile failed                        32
ccache internal error             153886
cache file missing                    11
unsupported compiler option      2063671
no input file                    1069038
files in cache                     24705
cache size                          17.3 Gbytes
max cache size                      20.0 Gbytes

also, I use:

CCACHE_SLOPPINESS=include_file_mtime
CCACHE_DIR=/pmi/cmpbib/.ccache/
CCACHE_HARDLINK=1


Eric
Comment 1 Joel Rosdahl 2014-01-01 19:42:47 UTC
Is the problem reproducible? If so, could you describe how to do it?
Comment 2 Eric Chamberland 2014-01-04 15:40:49 UTC
The probleme is that I needed to continue to work, so I did a "ccache -C" and the compilation, of course, started to work again.

What should I do the next time I encounter this bug?

Thanks,

Eric
Comment 3 Joel Rosdahl 2014-01-08 18:50:30 UTC
(In reply to comment #2)
> The probleme is that I needed to continue to work, so I did a "ccache -C" and
> the compilation, of course, started to work again.
> 
> What should I do the next time I encounter this bug?

Preferably a stack trace from a core dump produced by a ccache compiled without optimization.