[valgrind] [Bug 359705] memcheck causes segfault on a dynamically-linked test from rustlang's test suite on i686

https://bugs.kde.org/show_bug.cgi?id=359705 --- Comment #7 from Julian Seward --- (In reply to infinity0 from comment #5) Greetings, Rustacean::infinity0. Is this bug still a problem for the Rust devs? If yes, are there up to date STRs? On the whole I am unhappy when Valgrind

[valgrind] [Bug 359705] memcheck causes segfault on a dynamically-linked test from rustlang's test suite on i686

https://bugs.kde.org/show_bug.cgi?id=359705 Philippe Waroquiers changed: What|Removed |Added CC|

[valgrind] [Bug 359705] memcheck causes segfault on a dynamically-linked test from rustlang's test suite on i686

https://bugs.kde.org/show_bug.cgi?id=359705 --- Comment #4 from Tom Hughes --- At least I thought it did, because I remember it being discussed recently, bit I can't find it right now... -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 359705] memcheck causes segfault on a dynamically-linked test from rustlang's test suite on i686

https://bugs.kde.org/show_bug.cgi?id=359705 --- Comment #3 from Tom Hughes --- What you're missing is that valgrind imposes it's own limit of 8Mb on the stack, which you have clearly hit given the size it reported. Just looking at the memory map won't help you. -- You are

[valgrind] [Bug 359705] memcheck causes segfault on a dynamically-linked test from rustlang's test suite on i686

https://bugs.kde.org/show_bug.cgi?id=359705 --- Comment #2 from infini...@pwned.gg --- We don't think that's the real reason. I don't know how to analyse such things but another Debian maintainer looked through the proc-mem map that I linked above, and had this to say: 15:48:15 infinity0: it

[valgrind] [Bug 359705] memcheck causes segfault on a dynamically-linked test from rustlang's test suite on i686

https://bugs.kde.org/show_bug.cgi?id=359705 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1