valgrind-users  

Messages by Thread

• • Re: [Valgrind-users] Multi-threading Dor Ben Dov
• [Valgrind-users] (no subject) Dor Ben Dov
  • [Valgrind-users] (no subject) Shivakumar G
  • [Valgrind-users] (no subject) Kissami Imad
  • Re: [Valgrind-users] detection of gcc version John Reiser
  • Re: [Valgrind-users] detection of gcc version Kissami Imad
  • Re: [Valgrind-users] detection of gcc version John Reiser
  • Re: [Valgrind-users] detection of gcc version Zack Weinberg
  • [Valgrind-users] (no subject) Jeffrey Walton
• [Valgrind-users] valgrind installation failed Alla _
  • Re: [Valgrind-users] valgrind installation failed Alexander Potapenko
  • Re: [Valgrind-users] valgrind installation failed Alla _
  • Re: [Valgrind-users] valgrind installation failed Alexander Potapenko
  • Re: [Valgrind-users] valgrind installation failed Alla _
• [Valgrind-users] Bug review Vasantha Ganesh K
• [Valgrind-users] Helgrind mutex_is_valid assert Tony Perrie
• [Valgrind-users] can memchecker mark memory as read-only ? Gilles Gouaillardet
  • Re: [Valgrind-users] can memchecker mark memory as read-only ? John Reiser
  • Re: [Valgrind-users] can memchecker mark memory as read-only ? Christoph Niethammer
• [Valgrind-users] Will the BBV tool support ARMv7 and ARMv8? Lennox Wu
  • Re: [Valgrind-users] Will the BBV tool support ARMv7 and ARMv8? Florian Krohm
• [Valgrind-users] valgrind + MPI: What's causing these reported errors? Florian Lindner
• [Valgrind-users] How to use valgrind with Python+Numpy+Theano Wenjie
• [Valgrind-users] Segfault, Assertion 'bad_scanned_addr >= VG_ROUNDUP (MPI / pthread program) Jim
  • Re: [Valgrind-users] Segfault, Assertion 'bad_scanned_addr >= VG_ROUNDUP (MPI / pthread program) Philippe Waroquiers
  • Re: [Valgrind-users] Segfault, Assertion 'bad_scanned_addr >= VG_ROUNDUP (MPI / pthread program) Philippe Waroquiers
• [Valgrind-users] what are the commands to check this scheduler code? Mandy Martino
  • Re: [Valgrind-users] what are the commands to check this scheduler code? Mandy Martino
  • [Valgrind-users] why number of cache miss do not decrease after optimize in ubuntu 12 in VMware player 12? Mandy Martino
  • [Valgrind-users] why miss rate decrease but number of misses increase in ubuntu 12 in vmware player 12 ? Mandy Martino
  • Re: [Valgrind-users] why miss rate decrease but number of misses increase in ubuntu 12 in vmware player 12 ? Josef Weidendorfer
  • Re: [Valgrind-users] why miss rate decrease but number of misses increase in ubuntu 12 in vmware player 12 ? Mandy Martino
  • Re: [Valgrind-users] why miss rate decrease but number of misses increase in ubuntu 12 in vmware player 12 ? Josef Weidendorfer
• [Valgrind-users] valgrind it doesn't work with Qt Creator in OS X Freddy Martinez Garcia
  • Re: [Valgrind-users] valgrind it doesn't work with Qt Creator in OS X paulf
  • Re: [Valgrind-users] valgrind it doesn't work with Qt Creator in OS X Freddy Martinez Garcia
• [Valgrind-users] Interesting program output errors on ARM Henry Gomersall
  • Re: [Valgrind-users] Interesting program output errors on ARM Henry Gomersall
• [Valgrind-users] Understand valgrind output when checking a fortran code for memory leaks kevin.lemorzadec
  • Re: [Valgrind-users] Understand valgrind output when checking a fortran code for memory leaks John Reiser
  • Re: [Valgrind-users] Understand valgrind output when checking a fortran code for memory leaks David Chapman
• [Valgrind-users] Bypass procedure size checking in Valgrind Wojciech Franczyk
  • Re: [Valgrind-users] Bypass procedure size checking in Valgrind Florian Krohm
• [Valgrind-users] Assertion 'eltSzB <= ddpa->poolSzB' failed David Hallas
  • Re: [Valgrind-users] Assertion 'eltSzB <= ddpa->poolSzB' failed Philippe Waroquiers
  • Re: [Valgrind-users] Assertion 'eltSzB <= ddpa->poolSzB' failed Philippe Waroquiers
  • Re: [Valgrind-users] Assertion 'eltSzB <= ddpa->poolSzB' failed David Hallas
  • Re: [Valgrind-users] Assertion 'eltSzB <= ddpa->poolSzB' failed Philippe Waroquiers
  • Re: [Valgrind-users] Assertion 'eltSzB <= ddpa->poolSzB' failed David Hallas
  • Re: [Valgrind-users] Assertion 'eltSzB <= ddpa->poolSzB' failed Philippe Waroquiers
  • Re: [Valgrind-users] Assertion 'eltSzB <= ddpa->poolSzB' failed David Hallas
  • Re: [Valgrind-users] Assertion 'eltSzB <= ddpa->poolSzB' failed David Hallas
  • Re: [Valgrind-users] Assertion 'eltSzB <= ddpa->poolSzB' failed Florian Krohm
  • Re: [Valgrind-users] Assertion 'eltSzB <= ddpa->poolSzB' failed Philippe Waroquiers
• [Valgrind-users] debugging GSequencer Joël Krähemann
• [Valgrind-users] Linux futexes in ARMv8 cause scaling issues? Karthik Sangaiah
• Re: [Valgrind-users] valgrind on pandaboard Alina
• [Valgrind-users] Strange warning: Ignoring non-Dwarf2/3/4 block in .debug_info ISHIKAWA,chiaki
  • Re: [Valgrind-users] Strange warning: Ignoring non-Dwarf2/3/4 block in .debug_info Julian Seward
  • Re: [Valgrind-users] Strange warning: Ignoring non-Dwarf2/3/4 block in .debug_info ISHIKAWA,chiaki
  • Re: [Valgrind-users] Strange warning: Ignoring non-Dwarf2/3/4 block in .debug_info ISHIKAWA,chiaki
  • Re: [Valgrind-users] Strange warning: Ignoring non-Dwarf2/3/4 block in .debug_info Philippe Waroquiers
  • Re: [Valgrind-users] Strange warning: Ignoring non-Dwarf2/3/4 block in .debug_info ISHIKAWA,chiaki
• [Valgrind-users] Query on valkyrie kantheti prajyodh
• [Valgrind-users] Is Valgrind supported on ARM Cortex-M3? Sean Condon
  • Re: [Valgrind-users] Is Valgrind supported on ARM Cortex-M3? John Reiser
• Re: [Valgrind-users] Valgrind is broken on recent linux kernel Mike Krinkin
  • Re: [Valgrind-users] Valgrind is broken on recent linux kernel Tom Hughes
• [Valgrind-users] Unrecognized Instruction in Ubuntu ARM library Jim Starkey
  • Re: [Valgrind-users] Unrecognized Instruction in Ubuntu ARM library Jeffrey Walton
  • Re: [Valgrind-users] Unrecognized Instruction in Ubuntu ARM library Tom Hughes
  • Re: [Valgrind-users] Unrecognized Instruction in Ubuntu ARM library Jim Starkey
• [Valgrind-users] Information on adding unknown instructions due to "illegal opcde"? Jeffrey Walton
  • Re: [Valgrind-users] Information on adding unknown instructions due to "illegal opcde"? Philippe Waroquiers
  • Re: [Valgrind-users] Information on adding unknown instructions due to "illegal opcde"? John Reiser
  • Re: [Valgrind-users] Information on adding unknown instructions due to "illegal opcde"? Julian Seward
• [Valgrind-users] x86 to VEX translation process Jon Stephens
  • Re: [Valgrind-users] x86 to VEX translation process Philippe Waroquiers
• [Valgrind-users] Support for Mac OSX 10.11 clarification Sean Au
  • Re: [Valgrind-users] Support for Mac OSX 10.11 clarification Konstantin Tokarev
  • Re: [Valgrind-users] Support for Mac OSX 10.11 clarification Sean McBride
  • Re: [Valgrind-users] Support for Mac OSX 10.11 clarification Sean Au
• [Valgrind-users] Using callgrind for getting cache misses and data reads of a python program Rohit Takhar
  • Re: [Valgrind-users] Using callgrind for getting cache misses and data reads of a python program Josef Weidendorfer
• [Valgrind-users] unhandle instruction with valgrind on armv8 pritesh
• [Valgrind-users] Wrong function names (or line numbers) in ms_print output Nikolaus Rath
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Philippe Waroquiers
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Nikolaus Rath
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Philippe Waroquiers
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Nikolaus Rath
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Nikolaus Rath
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Philippe Waroquiers
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Nikolaus Rath
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Philippe Waroquiers
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Philippe Waroquiers
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Nikolaus Rath
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Nikolaus Rath
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Philippe Waroquiers
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Nikolaus Rath
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Matthias Schwarzott
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Nikolaus Rath
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Philippe Waroquiers
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Nikolaus Rath
  • Re: [Valgrind-users] Wrong function names (or line numbers) in ms_print output Philippe Waroquiers
• [Valgrind-users] DRD: pt_threadid != INVALID_POSIX_THREADID assertion Jonathan Rajotte Julien
  • Re: [Valgrind-users] DRD: pt_threadid != INVALID_POSIX_THREADID assertion Jonathan Rajotte Julien
• [Valgrind-users] POW() function behaving different when running in valgrind? Wilfried Goesgens
  • Re: [Valgrind-users] POW() function behaving different when running in valgrind? Tom Hughes
  • Re: [Valgrind-users] POW() function behaving different when running in valgrind? John Reiser
• [Valgrind-users] Fuzz testing with Valgrind? Dallman, John
  • Re: [Valgrind-users] Fuzz testing with Valgrind? Ildar Isaev
• [Valgrind-users] libxml2 multithreading errors in helgrind Hovnatan Karapetyan
• [Valgrind-users] Removal of db-attach Maurice van der Pot
  • Re: [Valgrind-users] Removal of db-attach Philippe Waroquiers
  • Re: [Valgrind-users] Removal of db-attach John Reiser
  • Re: [Valgrind-users] Removal of db-attach Philippe Waroquiers
• [Valgrind-users] some questions about valgrind massif yoma sophian
  • Re: [Valgrind-users] some questions about valgrind massif Azat Khuzhin
  • Re: [Valgrind-users] some questions about valgrind massif yoma sophian
  • Re: [Valgrind-users] some questions about valgrind massif Philippe Waroquiers
  • Re: [Valgrind-users] some questions about valgrind massif yoma sophian
  • Re: [Valgrind-users] some questions about valgrind massif Philippe Waroquiers
  • Re: [Valgrind-users] some questions about valgrind massif Philippe Waroquiers
  • Re: [Valgrind-users] some questions about valgrind massif yoma sophian
  • Re: [Valgrind-users] some questions about valgrind massif Philippe Waroquiers
  • Re: [Valgrind-users] some questions about valgrind massif Philippe Waroquiers
  • Re: [Valgrind-users] some questions about valgrind massif yoma sophian
  • Re: [Valgrind-users] some questions about valgrind massif Ivo Raisr
  • Re: [Valgrind-users] some questions about valgrind massif yoma sophian
  • Re: [Valgrind-users] some questions about valgrind massif yoma sophian
  • Re: [Valgrind-users] some questions about valgrind massif Philippe Waroquiers
• [Valgrind-users] cross-compilation praveen pujari
• [Valgrind-users] pthread - sem_post problem... Jan Kubalek
  • Re: [Valgrind-users] pthread - sem_post problem... David Chapman
  • Re: [Valgrind-users] pthread - sem_post problem... Jan Kubalek
  • Re: [Valgrind-users] pthread - sem_post problem... David Chapman
  • Re: [Valgrind-users] pthread - sem_post problem... Jan Kubalek
• [Valgrind-users] Memcheck warning Mccall, Kurt E. (JSC-EG411)
  • Re: [Valgrind-users] Memcheck warning Philippe Waroquiers
• [Valgrind-users] [SPAM] {SPAM?} Fw: new message Thierry Lahaye
• [Valgrind-users] [SPAM] Fw: new message Lukasz Marek
  • [Valgrind-users] [SPAM] Fw: new message Carl Ponder
  • [Valgrind-users] [SPAM] Fw: new message Alain Vermeiren
  • [Valgrind-users] [SPAM] Fw: new message Julian Seward
  • [Valgrind-users] [SPAM] Fw: new message Alain Vermeiren
  • [Valgrind-users] [SPAM] Fw: new message Carl Ponder
  • [Valgrind-users] [SPAM] Fw: new message lchquan
  • [Valgrind-users] [SPAM] Fw: new message Thierry Lahaye
  • [Valgrind-users] [SPAM] Fw: new message Florian Krohm
  • [Valgrind-users] [SPAM] Fw: new message Thierry Lahaye
  • [Valgrind-users] [SPAM] Fw: new message Thierry Lahaye
  • [Valgrind-users] [SPAM] Fw: new message Van Snyder
  • [Valgrind-users] [SPAM] Fw: new message Van Snyder
  • [Valgrind-users] [SPAM] Fw: new message Van Snyder
  • [Valgrind-users] [SPAM] Fw: new message Van Snyder
  • [Valgrind-users] [SPAM] Fw: new message Vronique Patigny
  • [Valgrind-users] [SPAM] Fw: new message Carl Ponder
  • [Valgrind-users] [SPAM] Fw: new message Mounira BENCHEKROUN
  • [Valgrind-users] [SPAM] Fw: new message Philippe Waroquiers
  • [Valgrind-users] [SPAM] Fw: new message Benoit Escarmelle
  • [Valgrind-users] [SPAM] Fw: new message m.bibby
  • [Valgrind-users] [SPAM] Fw: new message Benoit Escarmelle
• [Valgrind-users] Fw: new message Lukasz Marek
  • [Valgrind-users] Fw: new message Julian Seward
  • [Valgrind-users] Fw: new message Julian Seward
  • [Valgrind-users] Fw: new message Alain Vermeiren
  • [Valgrind-users] Fw: new message Lukasz Marek
  • [Valgrind-users] Fw: new message Lukasz Marek
  • [Valgrind-users] Fw: new message lchquan
  • [Valgrind-users] Fw: new message lchquan
  • [Valgrind-users] Fw: new message Mounira BENCHEKROUN
  • [Valgrind-users] Fw: new message Carl Ponder
  • [Valgrind-users] Fw: new message Thierry Lahaye
• [Valgrind-users] Trying to figure out if errors from app linked with IntelMPI are spurious Ramsey, James J CIV USARMY RDECOM ARL (US)
  • Re: [Valgrind-users] Trying to figure out if errors from app linked with IntelMPI are spurious Ramsey, James J CIV USARMY RDECOM ARL (US)
  • Re: [Valgrind-users] Trying to figure out if errors from app linked with IntelMPI are spurious Ramsey, James J CIV USARMY RDECOM ARL (US)
  • Re: [Valgrind-users] Trying to figure out if errors from app linked with IntelMPI are spurious John Reiser
  • Re: [Valgrind-users] Trying to figure out if errors from app linked with IntelMPI are spurious Ramsey, James J CIV USARMY RDECOM ARL (US)
• [Valgrind-users] valgrind and gdb Marco Cisternino
  • Re: [Valgrind-users] valgrind and gdb John Reiser
  • Re: [Valgrind-users] valgrind and gdb Marco Cisternino
  • Re: [Valgrind-users] valgrind and gdb John Reiser
  • Re: [Valgrind-users] valgrind and gdb Philippe Waroquiers
  • Re: [Valgrind-users] valgrind and gdb Philippe Waroquiers
  • Re: [Valgrind-users] valgrind and gdb Marco Cisternino
• [Valgrind-users] porition names length Marco Cisternino
  • Re: [Valgrind-users] porition names length Florian Krohm
  • Re: [Valgrind-users] porition names length Marco Cisternino
  • Re: [Valgrind-users] porition names length Marco Cisternino
• [Valgrind-users] Developing a tool using C++STL William Good
• [Valgrind-users] ARMv8 Vectorized Double-precision Instructions Karthik Sangaiah
  • Re: [Valgrind-users] ARMv8 Vectorized Double-precision Instructions Julian Seward
  • Re: [Valgrind-users] ARMv8 Vectorized Double-precision Instructions Karthik Sangaiah
• [Valgrind-users] Detect Global Offset Table (GOT) changes or corruption? Jeffrey Walton
  • Re: [Valgrind-users] Detect Global Offset Table (GOT) changes or corruption? jreiser
  • Re: [Valgrind-users] Detect Global Offset Table (GOT) changes or corruption? Julian Seward
  • Re: [Valgrind-users] Detect Global Offset Table (GOT) changes or corruption? Jeffrey Walton
  • Re: [Valgrind-users] Detect Global Offset Table (GOT) changes or corruption? Jeffrey Walton
• [Valgrind-users] Valgrind Bad option: --vgdb-error=0 Ulrich-Lorenz Schlüter
  • Re: [Valgrind-users] Valgrind Bad option: --vgdb-error=0 Tom Hughes

• Earlier messages
• Later messages