https://bugs.kde.org/show_bug.cgi?id=497977
Philippe Waroquiers <philippe.waroqui...@skynet.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philippe.waroquiers@skynet.
| |be
--- Comment #1 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
Here is the piece of code that leads to this message:
Bool MC_(record_fishy_value_error) ( ThreadId tid, const HChar *function_name,
const HChar *argument_name, SizeT value)
{
MC_Error extra;
tl_assert(VG_INVALID_THREADID != tid);
if ((SSizeT)value >= 0) return False; // not a fishy value
....
As you can see, the (unsigned) SizeT value is explicitly casted to a signed
type SSizeT and compared to 0.
While technically/formally, valgrind should not complain about the provided
value and/or should not speak about negative values,
this is an explicit decision to have this behavior as such values will
typically be a real user bug.
--
You are receiving this mail because:
You are watching all bug changes.
