[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 loading the opti

[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 Julian Seward
https://bugs.kde.org/show_bug.cgi?id=380037 Julian Seward changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[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 valgr

[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 com

[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 Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=380037 --- Comment #2 from Tom Hughes --- By the way the specific problem you're seeing here is that asan is trying to make sure it's intercepting malloc etc but of course valgrind also wants to do the same thing and they can't both do so. -- You are receivi

[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 Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=380037 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes --