https://bugs.kde.org/show_bug.cgi?id=497977
Florian Krohm <flo2...@eich-krohm.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |flo2...@eich-krohm.de
--- Comment #9 from Florian Krohm <flo2...@eich-krohm.de> ---
(In reply to Vincent Lefèvre from comment #0)
> [...]
> ==1153312== Argument 'size' of function malloc has a fishy (possibly
> negative) value: -1
I agree that this message could be improved. Clearly, the bit pattern being
passed as 'size' argument is being
interpreted as an unsigned value. So it cannot possibly be negative.
Perhaps:
Argument 'size' of function malloc is excessively large: <value in hex>.
Perhaps a negative value of <negative value here> was passed.
I guess most people will agree that ~(SizeT)0 >>1 as malloc size is also likely
a symptom of a bug. But as it does not pass valgrind's fishiness definition
there will be no complaint. Which makes me think that being able to provide a
fishy value threshold on the command line might be worth considering.
--
You are receiving this mail because:
You are watching all bug changes.
