[frameworks-kcrash] [Bug 336833] [Valgrind] "Invalid read of size 4" in KCrash::setCrashHandler(void (*)(int)) (qstring.h:89)

https://bugs.kde.org/show_bug.cgi?id=336833 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED

[frameworks-kcrash] [Bug 336833] [Valgrind] "Invalid read of size 4" in KCrash::setCrashHandler(void (*)(int)) (qstring.h:89)

https://bugs.kde.org/show_bug.cgi?id=336833 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular

[frameworks-kcrash] [Bug 336833] [Valgrind] "Invalid read of size 4" in KCrash::setCrashHandler(void (*)(int)) (qstring.h:89)

https://bugs.kde.org/show_bug.cgi?id=336833 Justin Zobel changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|---

[frameworks-kcrash] [Bug 336833] [Valgrind] "Invalid read of size 4" in KCrash::setCrashHandler(void (*)(int)) (qstring.h:89)

https://bugs.kde.org/show_bug.cgi?id=336833 --- Comment #2 from David Faure --- Ah, what is (was) the contents of your $DISPLAY environment variable? -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kcrash] [Bug 336833] [Valgrind] "Invalid read of size 4" in KCrash::setCrashHandler(void (*)(int)) (qstring.h:89)

https://bugs.kde.org/show_bug.cgi?id=336833 --- Comment #1 from David Faure --- Does this still happen? When I valgrind the test program from kcrash (which also ends up in kcrashInitialize()), valgrind doesn't complain. 64 bit system, not 32 bits, right? -- You are receiving