https://bugs.kde.org/show_bug.cgi?id=400783
Julian Seward changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=400783
--- Comment #5 from Tom Hughes ---
Look there is basically nothing we can do with the information you have
provided - the stack trace is incomplete because the symbols appear to have
been stripped and you're using an obscure distribution that I doubt a
https://bugs.kde.org/show_bug.cgi?id=400783
--- Comment #4 from Andrew Pennebaker ---
I do not see this behavior with earlier versions of valgrind such as 3.12. It’s
worth pointing out that this fallacious free() warning is happening on Void
Linux, compared to no fallacious warnings in Debian.
-
https://bugs.kde.org/show_bug.cgi?id=400783
--- Comment #3 from Tom Hughes ---
The only reference to valgrind in that stack trace is to our replacement free
routine which has detected the problem - the actual problem is in the dynlink.c
code about that which has apparently passed an invalid point
https://bugs.kde.org/show_bug.cgi?id=400783
--- Comment #2 from Andrew Pennebaker ---
When I comment out all of my free()'s, valgrind continues to complain "Invalid
free()", and also indicates sections in the valgrind code, not my code.
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=400783
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #1 from Tom Hughes --
