valgrind-users  

Messages by Thread

• [Valgrind-users] Semaphore error on Helgrind and Drd? Paulo Ferreira
• [Valgrind-users] Valgrind-3.23.0 is available Mark Wielaard
• [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing Mark Wielaard
  • Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing Simon Sobisch
  • Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing Paul Floyd via Valgrind-users
  • Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing Simon Sobisch
  • Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing Paul Floyd via Valgrind-users
  • Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing Simon Sobisch
  • Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing Paul Floyd via Valgrind-users
  • Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing Simon Sobisch
  • Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing Carl Love via Valgrind-users
  • Re: [Valgrind-users] Valgrind-3.23.0.RC2 is available for testing Paul Floyd via Valgrind-users
• [Valgrind-users] Valgrind-3.23.0.RC1 is available for testing Mark Wielaard
  • Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.23.0.RC1 is available for testing Mark Wielaard
  • Re: [Valgrind-users] Valgrind-3.23.0.RC1 is available for testing Carl Love via Valgrind-users
  • Re: [Valgrind-users] Valgrind-3.23.0.RC1 is available for testing Mark Wielaard
  • Re: [Valgrind-users] Valgrind-3.23.0.RC1 is available for testing Carl Love via Valgrind-users
  • Re: [Valgrind-users] Valgrind-3.23.0.RC1 is available for testing Paul Floyd via Valgrind-users
• [Valgrind-users] Always investigate valgrind memcheck errors [rjo...@redhat.com: Re: xz backdoor] Mark Wielaard
  • Re: [Valgrind-users] Always investigate valgrind memcheck errors [rjo...@redhat.com: Re: xz backdoor] Paul Floyd via Valgrind-users
• [Valgrind-users] Docker Support jinesh gada
  • Re: [Valgrind-users] Docker Support Paul Floyd via Valgrind-users
  • Re: [Valgrind-users] Docker Support jinesh gada
• [Valgrind-users] Missing the library file /lib/valgrind/libmpiwrap-<platform>.so Rambaks, Andris
  • Re: [Valgrind-users] Missing the library file /lib/valgrind/libmpiwrap-<platform>.so Simon Sobisch
  • Re: [Valgrind-users] Missing the library file /lib/valgrind/libmpiwrap-<platform>.so Rambaks, Andris
• [Valgrind-users] FOSDEM 2024, Debuggers and Analysis tools devroom Mark Wielaard
• [Valgrind-users] thread not created when program executed with valgrind JD Silence
  • Re: [Valgrind-users] thread not created when program executed with valgrind Paul Floyd
  • [Valgrind-users] Fwd: thread not created when program executed with valgrind JD Silence
• [Valgrind-users] A thousand bugs Mark Wielaard
• [Valgrind-users] Valgrind-3.22.0 is available Mark Wielaard
• [Valgrind-users] Valgrind-3.22.0.RC2 is available for testing Mark Wielaard
  • Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.22.0.RC2 is available for testing Mark Wielaard
  • Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.22.0.RC2 is available for testing Paul Floyd
  • Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.22.0.RC2 is available for testing Mark Wielaard
  • Re: [Valgrind-users] Valgrind-3.22.0.RC2 is available for testing Paul Floyd
• [Valgrind-users] Valgrind-3.22.0.RC1 is available for testing Mark Wielaard
  • Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.22.0.RC1 is available for testing Mark Wielaard
• [Valgrind-users] Suspect "uninitialised value(s)" error Karl Robillard via Valgrind-users
  • Re: [Valgrind-users] Suspect "uninitialised value(s)" error Karl Robillard via Valgrind-users
  • Re: [Valgrind-users] Suspect "uninitialised value(s)" error Paul Floyd
  • Re: [Valgrind-users] Suspect "uninitialised value(s)" error Tom Hughes via Valgrind-users
  • Re: [Valgrind-users] Suspect "uninitialised value(s)" error Paul Floyd
  • Re: [Valgrind-users] Suspect "uninitialised value(s)" error Karl Robillard via Valgrind-users
  • Re: [Valgrind-users] Suspect "uninitialised value(s)" error Karl Robillard via Valgrind-users
• [Valgrind-users] valgrind usage in arm board ramakanth varala
  • Re: [Valgrind-users] valgrind usage in arm board ramakanth varala
  • Re: [Valgrind-users] valgrind usage in arm board John Reiser
  • Re: [Valgrind-users] valgrind usage in arm board ramakanth varala
  • Re: [Valgrind-users] valgrind usage in arm board John Reiser
  • Re: [Valgrind-users] valgrind usage in arm board ramakanth varala
• [Valgrind-users] how to proceed when faced with malloc error Jed Reynolds
  • Re: [Valgrind-users] how to proceed when faced with malloc error Julian Seward
• [Valgrind-users] Help Domenico Panella
  • Re: [Valgrind-users] Help Floyd, Paul
  • Re: [Valgrind-users] Help Domenico Panella
  • Re: [Valgrind-users] Help John Reiser
  • Re: [Valgrind-users] Help Floyd, Paul
• [Valgrind-users] getting type information for local and global variables? Tia Newhall
  • Re: [Valgrind-users] getting type information for local and global variables? Mark Wielaard
  • Re: [Valgrind-users] getting type information for local and global variables? Tia Newhall
  • Re: [Valgrind-users] getting type information for local and global variables? Mark Wielaard
• [Valgrind-users] Does Valgrind support AMD Ryzen 5 5600X processors Stuart Foster via Valgrind-users
  • Re: [Valgrind-users] Does Valgrind support AMD Ryzen 5 5600X processors Simon Sobisch
  • Re: [Valgrind-users] Does Valgrind support AMD Ryzen 5 5600X processors Tom Hughes via Valgrind-users
  • Re: [Valgrind-users] Does Valgrind support AMD Ryzen 5 5600X processors John Reiser
  • Re: [Valgrind-users] Does Valgrind support AMD Ryzen 5 5600X processors Nicholas Nethercote
  • Re: [Valgrind-users] Does Valgrind support AMD Ryzen 5 5600X processors Stuart Foster via Valgrind-users
• [Valgrind-users] Issues in the callgrind output report Pavankumar S V
  • Re: [Valgrind-users] Issues in the callgrind output report Floyd, Paul
• [Valgrind-users] valgrind gets fatal signal when particular syscall is made by an executable Daniel Fishman
  • Re: [Valgrind-users] valgrind gets fatal signal when particular syscall is made by an executable John Reiser
  • Re: [Valgrind-users] valgrind gets fatal signal when particular syscall is made by an executable Daniel Fishman
  • Re: [Valgrind-users] valgrind gets fatal signal when particular syscall is made by an executable Tom Hughes via Valgrind-users
• [Valgrind-users] unhandled instruction bytes for vmovdqu64 Simon Sobisch
  • Re: [Valgrind-users] unhandled instruction bytes for vmovdqu64 John Reiser
  • Re: [Valgrind-users] unhandled instruction bytes for vmovdqu64 Simon Sobisch
  • Re: [Valgrind-users] unhandled instruction bytes for vmovdqu64 Mark Wielaard
  • Re: [Valgrind-users] unhandled instruction bytes for vmovdqu64 Simon Sobisch
• [Valgrind-users] "Error accepting connection: Function not implemented", is this expected? mamsds
  • Re: [Valgrind-users] "Error accepting connection: Function not implemented", is this expected? John Reiser
  • Re: [Valgrind-users] "Error accepting connection: Function not implemented", is this expected? mamsds
  • Re: [Valgrind-users] "Error accepting connection: Function not implemented", is this expected? ISHIKAWA,chiaki
  • Re: [Valgrind-users] "Error accepting connection: Function not implemented", is this expected? John Reiser
  • Re: [Valgrind-users] "Error accepting connection: Function not implemented", is this expected? John Reiser
  • Re: [Valgrind-users] "Error accepting connection: Function not implemented", is this expected? mamsds
• Re: [Valgrind-users] [Valgrind-developers] RFC: support scalable vector model / riscv vector Wu, Fei
  • Re: [Valgrind-users] [Valgrind-developers] RFC: support scalable vector model / riscv vector Wu, Fei
  • Re: [Valgrind-users] [Valgrind-developers] RFC: support scalable vector model / riscv vector Petr Pavlu
  • Re: [Valgrind-users] [Valgrind-developers] RFC: support scalable vector model / riscv vector Wu, Fei
  • Re: [Valgrind-users] [Valgrind-developers] RFC: support scalable vector model / riscv vector Wu, Fei
  • Re: [Valgrind-users] [Valgrind-developers] RFC: support scalable vector model / riscv vector Petr Pavlu
  • Re: [Valgrind-users] [Valgrind-developers] RFC: support scalable vector model / riscv vector Wu, Fei
  • Re: [Valgrind-users] [Valgrind-developers] RFC: support scalable vector model / riscv vector Petr Pavlu
• [Valgrind-users] Valgrind-3.21.0 is available Mark Wielaard
• [Valgrind-users] tool=cachegrind always reports LL misses, even if the cache is bigger than the used memory Volker Dirr
  • Re: [Valgrind-users] tool=cachegrind always reports LL misses, even if the cache is bigger than the used memory Eliot Moss
  • Re: [Valgrind-users] tool=cachegrind always reports LL misses, even if the cache is bigger than the used memory John Reiser
• [Valgrind-users] Valgrind-3.21.0.RC2 is available for testing Mark Wielaard
  • Re: [Valgrind-users] Valgrind-3.21.0.RC2 is available for testing Paul Floyd
  • Re: [Valgrind-users] Valgrind-3.21.0.RC2 is available for testing Paul Floyd
  • Re: [Valgrind-users] Valgrind-3.21.0.RC2 is available for testing Paul Floyd
  • Re: [Valgrind-users] Valgrind-3.21.0.RC2 is available for testing Paul Floyd
• [Valgrind-users] unhandled instruction bytes folkert
  • Re: [Valgrind-users] unhandled instruction bytes Eliot Moss
  • Re: [Valgrind-users] unhandled instruction bytes folkert
  • Re: [Valgrind-users] unhandled instruction bytes Floyd, Paul
  • Re: [Valgrind-users] unhandled instruction bytes folkert
  • Re: [Valgrind-users] unhandled instruction bytes Mark Wielaard
• [Valgrind-users] Valgrind-3.21.0.RC1 is available for testing Mark Wielaard
  • Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.21.0.RC1 is available for testing Nicholas Nethercote
• [Valgrind-users] A bit more (pre-release) automation Mark Wielaard
• [Valgrind-users] RFC: changing Cachegrind default to `--cache-sim=no` Nicholas Nethercote
  • Re: [Valgrind-users] RFC: changing Cachegrind default to `--cache-sim=no` David Faure
  • Re: [Valgrind-users] RFC: changing Cachegrind default to `--cache-sim=no` Nicholas Nethercote
  • Re: [Valgrind-users] RFC: changing Cachegrind default to `--cache-sim=no` David Faure
  • Re: [Valgrind-users] RFC: changing Cachegrind default to `--cache-sim=no` Nicholas Nethercote
  • Re: [Valgrind-users] RFC: changing Cachegrind default to `--cache-sim=no` David Faure
• [Valgrind-users] RFC: proposal to remove user annotation from `cg_annotate` Nicholas Nethercote
  • Re: [Valgrind-users] RFC: proposal to remove user annotation from `cg_annotate` Nicholas Nethercote
  • Re: [Valgrind-users] RFC: proposal to remove user annotation from `cg_annotate` Nicholas Nethercote
• [Valgrind-users] about a stack fill option (as for malloc-fill and free-fill) Julien Allali
  • Re: [Valgrind-users] about a stack fill option (as for malloc-fill and free-fill) Paul Floyd
  • Re: [Valgrind-users] about a stack fill option (as for malloc-fill and free-fill) John Reiser
  • Re: [Valgrind-users] about a stack fill option (as for malloc-fill and free-fill) Paul Floyd
• [Valgrind-users] valgrind exits with an error when using mmap (mmap mdev device) ?????????? via Valgrind-users
  • Re: [Valgrind-users] valgrind exits with an error when using mmap (mmap mdev device) Floyd, Paul
• [Valgrind-users] Dependency issue with apt install Valgrind in Ubuntu Mate distro Jake Heke
• [Valgrind-users] Compilation fails on ARM Leon Pollak
  • Re: [Valgrind-users] Compilation fails on ARM Paul Floyd
  • Re: [Valgrind-users] Compilation fails on ARM Leon Pollak
  • Re: [Valgrind-users] Compilation fails on ARM Leon Pollak
  • Re: [Valgrind-users] Compilation fails on ARM John Reiser
  • Re: [Valgrind-users] Compilation fails on ARM Leon Pollak
  • Re: [Valgrind-users] Compilation fails on ARM John Reiser
  • Re: [Valgrind-users] Compilation fails on ARM Leon Pollak
• [Valgrind-users] Recursive `who-points-at` User 10482
  • Re: [Valgrind-users] Recursive `who-points-at` Philippe Waroquiers
  • Re: [Valgrind-users] Recursive `who-points-at` Eliot Moss
• Re: [Valgrind-users] Need Help Anand K R
  • Re: [Valgrind-users] Need Help Paul Floyd
  • Re: [Valgrind-users] Need Help John Reiser
• [Valgrind-users] Regarding use of Lackey to trace midway execution of a program SAI GOVARDHAN M C PES1UG19EC255PESU ECE Student
  • Re: [Valgrind-users] Regarding use of Lackey to trace midway execution of a program Eliot Moss
  • Re: [Valgrind-users] Regarding use of Lackey to trace midway execution of a program Philippe Waroquiers
• [Valgrind-users] Cache conflict detection support in cachegrind Ivica B
  • Re: [Valgrind-users] Cache conflict detection support in cachegrind Paul Floyd
  • Re: [Valgrind-users] Cache conflict detection support in cachegrind John Reiser
  • Re: [Valgrind-users] Cache conflict detection support in cachegrind Ivica B
  • Re: [Valgrind-users] Cache conflict detection support in cachegrind Eliot Moss
  • Re: [Valgrind-users] Cache conflict detection support in cachegrind Ivica B
  • Re: [Valgrind-users] Cache conflict detection support in cachegrind Eliot Moss
  • Re: [Valgrind-users] Cache conflict detection support in cachegrind Paul Floyd
  • Re: [Valgrind-users] Cache conflict detection support in cachegrind Ivica B
• [Valgrind-users] memory leak reported many times, but only one instance should be possible Gordon Messmer
  • Re: [Valgrind-users] memory leak reported many times, but only one instance should be possible Paul Floyd
  • Re: [Valgrind-users] memory leak reported many times, but only one instance should be possible Gordon Messmer
• [Valgrind-users] A weird memory leak with openmp task depend Chen Gang via Valgrind-users
  • Re: [Valgrind-users] A weird memory leak with openmp task depend Floyd, Paul
  • Re: [Valgrind-users] A weird memory leak with openmp task depend Chen Gang via Valgrind-users
• [Valgrind-users] client program compiled with pie Mark Roberts
  • Re: [Valgrind-users] client program compiled with pie Floyd, Paul
  • Re: [Valgrind-users] client program compiled with pie Chen Gang via Valgrind-users
• [Valgrind-users] Timer delete Domenico Panella
  • Re: [Valgrind-users] Timer delete Paul Floyd
  • Re: [Valgrind-users] Timer delete Philippe Waroquiers
  • Re: [Valgrind-users] Timer delete Domenico Panella
  • Re: [Valgrind-users] Timer delete John Reiser
  • Re: [Valgrind-users] Timer delete Domenico Panella
  • Re: [Valgrind-users] Timer delete Paul Floyd
  • Re: [Valgrind-users] Timer delete Philippe Waroquiers
  • Re: [Valgrind-users] Timer delete Mark Wielaard
  • Re: [Valgrind-users] Timer delete Paul Floyd
  • Re: [Valgrind-users] Timer delete Paul Floyd
• [Valgrind-users] Valgrind-3.20.0 is available Mark Wielaard
• [Valgrind-users] Valgrind-3.20.0.RC1 is available for testing Mark Wielaard
  • Re: [Valgrind-users] Valgrind-3.20.0.RC1 is available for testing Paul Floyd
  • Re: [Valgrind-users] Valgrind-3.20.0.RC1 is available for testing Mathieu Malaterre
  • Re: [Valgrind-users] Valgrind-3.20.0.RC1 is available for testing Mark Wielaard
  • Re: [Valgrind-users] Valgrind-3.20.0.RC1 is available for testing Mathieu Malaterre
  • Re: [Valgrind-users] Valgrind-3.20.0.RC1 is available for testing Paul Floyd
  • Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.20.0.RC1 is available for testing Philippe Waroquiers
  • Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.20.0.RC1 is available for testing Mark Wielaard
  • Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.20.0.RC1 is available for testing Philippe Waroquiers
  • Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.20.0.RC1 is available for testing Mark Wielaard
• [Valgrind-users] callgrind.out file size is zero Mahin Pandya
  • Re: [Valgrind-users] callgrind.out file size is zero Philippe Waroquiers
  • Re: [Valgrind-users] callgrind.out file size is zero Floyd, Paul
• [Valgrind-users] [Android] Warning linker with memcheck library $rik@nth
• [Valgrind-users] Valgrind not finding issue with writing/reading past array? Grant Schoep
  • Re: [Valgrind-users] Valgrind not finding issue with writing/reading past array? Philippe Waroquiers
  • Re: [Valgrind-users] Valgrind not finding issue with writing/reading past array? Tom Hughes via Valgrind-users
• [Valgrind-users] bug report: bugzilla refused to accept this saying it contains spam. But it doesn't. ISHIKAWA,chiaki
  • Re: [Valgrind-users] bug report: bugzilla refused to accept this saying it contains spam. But it doesn't. ISHIKAWA,chiaki
  • Re: [Valgrind-users] bug report: bugzilla refused to accept this saying it contains spam. But it doesn't. John Reiser
  • Re: [Valgrind-users] bug report: bugzilla refused to accept this saying it contains spam. But it doesn't. ISHIKAWA,chiaki
  • Re: [Valgrind-users] bug report: bugzilla refused to accept this saying it contains spam. But it doesn't. ISHIKAWA,chiaki
• [Valgrind-users] bug id as url --error-exitcode= David Anderson
• [Valgrind-users] Filed bug on --error-exitcode doc issue David Anderson

• Earlier messages