[valgrind] [Bug 380037] New: valgrind + AddressSanitizer: ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PR

2017-05-20 Thread Graham Leggett
https://bugs.kde.org/show_bug.cgi?id=380037 Bug ID: 380037 Summary: valgrind + AddressSanitizer: ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload

[valgrind] [Bug 380037] valgrind + AddressSanitizer: ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD

2017-05-20 Thread Graham Leggett
https://bugs.kde.org/show_bug.cgi?id=380037 --- Comment #3 from Graham Leggett --- Having completely rebuilt both gstreamer git-master and valgrind v3.12.0 from source using gcc v6.20 with AddressSanitizer disabled, I am still getting the same error: ==26049== ==26049==ASan runtime does not

[valgrind] [Bug 380037] valgrind + AddressSanitizer: ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD

2017-05-20 Thread Graham Leggett
https://bugs.kde.org/show_bug.cgi?id=380037 --- Comment #4 from Graham Leggett --- Turned out the session I was using to run valgrind had libasan preloaded with LD_PRELOAD, and this turns AddressSanitizer on and triggers this crash. Removing LD_PRELOAD produces the next crash, this time in

[valgrind] [Bug 322935] disInstr(arm): unhandled instruction: 0xF1010200, valgrind: Unrecognised instruction on Raspbian

2017-05-20 Thread Graham Leggett
https://bugs.kde.org/show_bug.cgi?id=322935 Graham Leggett changed: What|Removed |Added CC||minf...@sharp.fm --- Comment #38 from Graham

[valgrind] [Bug 380037] valgrind + AddressSanitizer: ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD

2017-05-22 Thread Graham Leggett
https://bugs.kde.org/show_bug.cgi?id=380037 --- Comment #6 from Graham Leggett --- For the record, bug that prevents valgrind running raised with the RPi people here: https://bugs.kde.org/show_bug.cgi?id=380037 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 380037] valgrind + AddressSanitizer: ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD

2017-05-22 Thread Graham Leggett
https://bugs.kde.org/show_bug.cgi?id=380037 --- Comment #7 from Graham Leggett --- Let's try that again. For the record, the bug with the RPi people is here: https://github.com/RPi-Distro/repo/issues/68 At their suggestion moving /etc/ld.so.preload out of the way to prevent the loadin

[valgrind] [Bug 322935] disInstr(arm): unhandled instruction: 0xF1010200, valgrind: Unrecognised instruction on Raspbian

2017-05-22 Thread Graham Leggett
https://bugs.kde.org/show_bug.cgi?id=322935 --- Comment #39 from Graham Leggett --- For the record, moving /etc/ld.so.preload out of the way and in the process disabling the RPI's memcpy optimisations causes valgrind to run correctly on the RPi. -- You are receiving this mail because: Yo