https://bugs.kde.org/show_bug.cgi?id=497977
--- Comment #12 from Vincent Lefèvre <vincent-...@vinc17.net> --- (In reply to Paul Floyd from comment #11) > In this case both signed and unsigned values are nonsense. I don't see that > as much of an improvement. The issue is not the value itself, but the fact that valgrind currently says that the value is negative. This gives confusing information for the user. When I first saw this error, I started to blame my compiler / C library for providing a signed size_t type. -- You are receiving this mail because: You are watching all bug changes.
