https://bugs.kde.org/show_bug.cgi?id=514059
Paul Floyd <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOT A BUG Status|REPORTED |RESOLVED --- Comment #1 from Paul Floyd <[email protected]> --- Memcheck has detected a bug in your code. After that, especially invalid writes, anything can happen. We do not make any promises that Valgrind will be able to continue in a correct manner. The same is true for all dynamic analysis tools as far as I know. What you can do is increase the redzone size, e.g., valgrind --redzone-size=128 ./build/main/lilycc test-files/test_compound.c That is the amount of slop that Valgrind adds surrounding each heap allocation. That makes it more robust in the face of invalid writes. I'm closing this as not a bug. If you fix the bug in your code and the segfault is still there please reopen this report. -- You are receiving this mail because: You are watching all bug changes.
