Re: [Valgrind-developers] Preparing for Valgrind 3.25.0 (April 23)

[Paul F. <pj...@wa...>]

One other thing.

https://bugs.kde.org/show_bug.cgi?id=497977

Making a change so that the 'fishy' warnings show both signed and 
unsigned values is pretty straightforward.

The guy the reported the bugzi item couldn't get it into his head that 
you can call malloc and family with a signed value which gets implicitly 
converted to size_t. This problem came up at work last week, and it was 
another case of signed arithmetic wrapping and becoming negative.

Other than artificial testcases using values in the top half of the 
64bit unsigned value range I don't see this happening in the real world 
and so can't see much benefit in making this change.

Does anyone else think that showing the unsigned value would be useful?

A+
Paul