Bug 509184

Summary: 3.25.1
Product: [Developer tools] valgrind Reporter: Jacob Doherty <dev>
Component: generalAssignee: Julian Seward <jseward>
Status: RESOLVED NOT A BUG    
Severity: minor    
Priority: NOR    
Version First Reported In: 3.25.0   
Target Milestone: ---   
Platform: Debian stable   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Jacob Doherty 2025-09-06 10:31:12 UTC 
SUMMARY
valgrind --version reports: 3.24.0 when running 3.25.1

I downloaded the 3.25.1 source package and configured and installed from this URL:
https://sourceware.org/pub/valgrind/valgrind-3.25.1.tar.bz2

Inside I can see files modified in May 2025 so it looks like an updated version:

-rw-r--r--  1 myuser myuser  52101 2025-05-20 23:00:34.000000000 +1200 aclocal.m4
-rw-r--r--  1 myuser myuser   3521 2025-05-20 22:59:39.000000000 +1200 AUTHORS
-rwxr-xr-x  1 myuser myuser    460 2025-05-20 22:59:39.000000000 +1200 autogen.sh

Double checked 'which valgrind' which appears to point to the right compiled binary.
Can't see any other sources for valgrind binary (checked apt packages not installed etc).

STEPS TO REPRODUCE
1.  Configure, build and install from source using the 3.25.1 package.
2.  Check 'valgrind --version'

OBSERVED RESULT
myuser@debian:~$ valgrind --version
valgrind-3.24.0

EXPECTED RESULT
myuser@debian:~$ valgrind --version
valgrind-3.25.1
Comment 1 Jacob Doherty 2025-09-07 01:41:23 UTC 
After a reboot following the new 13.1 Debian release this appears to be behaving correctly.
Possibly something with my PATH or shell not picking up the right binary, but the correct version number is now being reported.
Apologies for the noise!