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

[Florian K. <fl...@ei...>]

On 10.04.25 21:35, Paul Floyd via Valgrind-developers wrote:
> 
> 
> 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.
> 

Yes. In https://bugs.kde.org/show_bug.cgi?id=497977#c9 I had recommended to 
change the wording like so:

Argument 'size' of function malloc is excessively large: <value in hex>.
Perhaps a negative  value of <negative value here> was passed.

The person who had opened the BZ considered that change an improvement (in 
comment #10).

Cheers,
   Florian