[Valgrind-users] Valgrind-3.25.0 is available

2025-04-25 Thread Mark Wielaard
We are pleased to announce a new release of Valgrind, version 3.25.0, available from https://valgrind.org/downloads/current.html. This release adds initial support for RISCV64/Linux, the GDB remote packet 'x', zstd compressed debug sections, Linux Test Project testsuite integration, numerous fixes

Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.25.0.RC2 is available for testing

2025-04-25 Thread Mark Wielaard
Hi Jeevitha, On Fri, 2025-04-25 at 13:15 +, P Jeevitha wrote: > Hi Everyone, > valgrind-3.25.0.RC2 also looks good on Power and that there are no issues > requiring fixes before releasing . Thanks again. I have just tagged the final 3.25.0 release in git. Will update the website and then ann

Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.25.0.RC1 is available for testing

2025-04-25 Thread Mark Wielaard
Hi Jeevitha, On Fri, 2025-04-25 at 11:52 +, P Jeevitha wrote: > Hi Everyone, > > valgrind-3.25.0.RC1 looks good on Power and that there are no issues > requiring fixes before releasing  Valgrind 3.25 Thanks so much for testing. The results do indeed look good. I am going to prepare the 3.25

Re: [Valgrind-users] Need support in debugging Valgrind 3.18 glibc segv error

2025-04-25 Thread Philippe Waroquiers via Valgrind-users
Yes, VALGRIND_MAKE_MEM_DEFINED is the correct solution. Philippe On Fri, 2025-04-25 at 03:27 +0530, kiran hardas wrote: > Hi Team, > > Thanks Philippe for your response. I have now used these > macros VALGRIND_MAKE_MEM_DEFINED after wherever i am attaching to the shared > memory to > mark it val