Summary: | Valgrind becomes noisy when compiled with gcc 4.9 | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | dimitry <dimitry> |
Component: | memcheck | Assignee: | Julian Seward <jseward> |
Status: | REPORTED --- | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 3.10 SVN | ||
Target Milestone: | --- | ||
Platform: | Android | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
dimitry
2015-05-27 18:45:03 UTC
(In reply to dimitry from comment #0) > This is what happens when valgrind is recompiled using gcc 4.9 > [..] Dmitry, just to be clear about this: are you saying that compiling valgrind with gcc 4.9 produces all this noise, even when the AOSP and all other code is still compiled with 4.8? Or do you mean "when entire system (including valgrind) is compiled with 4.9, I get all this noise that I didn't when the entire system was compiled with 4.8" ? I need to know in order to begin guessing what happened. yes this is correct only valgrind was recompiled with gcc 4.8... ... the rest of the code in aosp was compiled with gcc 4.9 So if I understand correctly, basically the bug is that memcheck is noisy on gcc 4.9 compiled code. Yes? yes. but interestingly only if valgrind is compiled with gcc 4.9 as well. If platform is compiled with gcc 4.9 and valgrind with gcc 4.8 it becomes less noisy.. |