valgrind-users  

Messages by Thread

• • Re: [Valgrind-users] Valgrind, Yocto tunning on arm flags David Lerner
  • Re: [Valgrind-users] Valgrind, Yocto tunning on arm flags David Andrey
• [Valgrind-users] Large amount of instructions when profiling an empty program? Jon
  • Re: [Valgrind-users] Large amount of instructions when profiling an empty program? Philippe Waroquiers
  • Re: [Valgrind-users] Large amount of instructions when profiling an empty program? Julian Seward
  • Re: [Valgrind-users] Large amount of instructions when profiling an empty program? John Reiser
• [Valgrind-users] how to kill a target program right after memcheck finds an memory error sean jinu
  • Re: [Valgrind-users] how to kill a target program right after memcheck finds an memory error Philippe Waroquiers
• [Valgrind-users] Can valgrind print the used "uninitialized value" and its size? ISHIKAWA,chiaki
  • Re: [Valgrind-users] Can valgrind print the used "uninitialized value" and its size? Maurice van Swaaij
  • Re: [Valgrind-users] Can valgrind print the used "uninitialized value" and its size? Philippe Waroquiers
  • Re: [Valgrind-users] Can valgrind print the used "uninitialized value" and its size? ISHIKAWA,chiaki
• [Valgrind-users] Reg : Posting Valgrind Queries to lists. evv rajesh
• [Valgrind-users] Query on Numa architecture friendly memory allocation profiling rajsing mohapatro
  • Re: [Valgrind-users] Query on Numa architecture friendly memory allocation profiling Josef Weidendorfer
• [Valgrind-users] Invalid write at _dl_start_user Zhu, Yanwen
• [Valgrind-users] vex mips->IR: unhandled instruction bytes Zhu, Yanwen
• [Valgrind-users] Valgrind: FATAL: aspacem assertion failed: john
  • Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed: Julian Seward
  • Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed: John OSullivan
  • Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed: Julian Seward
  • Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed: Florian Krohm
  • Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed: Julian Seward
  • Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed: John OSullivan
  • Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed: John OSullivan
  • Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed: Tom Hughes
  • Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed: Florian Krohm
  • Re: [Valgrind-users] Valgrind: FATAL: aspacem assertion failed: John O'Sullivan
• [Valgrind-users] Where is the list of supported clang versions? Lin Chuan
  • Re: [Valgrind-users] Where is the list of supported clang versions? John Reiser
  • Re: [Valgrind-users] Where is the list of supported clang versions? Calvin Cheng
  • Re: [Valgrind-users] Where is the list of supported clang versions? Julian Seward
  • Re: [Valgrind-users] Where is the list of supported clang versions? Calvin Cheng
  • Re: [Valgrind-users] Where is the list of supported clang versions? Calvin Cheng
• [Valgrind-users] Bug / typo saving altivec register r25 Lerner, Dave
  • Re: [Valgrind-users] Bug / typo saving altivec register r25 Philippe Waroquiers
• [Valgrind-users] valgrind out of memory error Zhu, Yanwen
  • Re: [Valgrind-users] valgrind out of memory error Philippe Waroquiers
  • Re: [Valgrind-users] valgrind out of memory error Zhu, Yanwen
  • Re: [Valgrind-users] valgrind out of memory error Zhu, Yanwen
  • Re: [Valgrind-users] valgrind out of memory error Philippe Waroquiers
  • Re: [Valgrind-users] valgrind out of memory error Zhu, Yanwen
  • Re: [Valgrind-users] valgrind out of memory error Philippe Waroquiers
  • Re: [Valgrind-users] valgrind out of memory error Zhu, Yanwen
  • Re: [Valgrind-users] valgrind out of memory error Philippe Waroquiers
  • Re: [Valgrind-users] valgrind out of memory error Julian Seward
  • Re: [Valgrind-users] valgrind out of memory error Zhu, Yanwen
  • Re: [Valgrind-users] valgrind out of memory error Zhu, Yanwen
  • Re: [Valgrind-users] valgrind out of memory error Tom Hughes
  • Re: [Valgrind-users] valgrind out of memory error Maurice van Swaaij
  • Re: [Valgrind-users] valgrind out of memory error Philippe Waroquiers
• [Valgrind-users] fuse filesystem syscall deadlocks Atalay Ozgovde
  • Re: [Valgrind-users] fuse filesystem syscall deadlocks Philippe Waroquiers
  • Re: [Valgrind-users] fuse filesystem syscall deadlocks Julian Seward
  • Re: [Valgrind-users] fuse filesystem syscall deadlocks Atalay Ozgovde
  • Re: [Valgrind-users] fuse filesystem syscall deadlocks Atalay Ozgovde
  • Re: [Valgrind-users] fuse filesystem syscall deadlocks Philippe Waroquiers
  • Re: [Valgrind-users] fuse filesystem syscall deadlocks Atalay Ozgovde
• [Valgrind-users] make dies: " /usr/bin/ar: libcoregrind_amd64_linux_a-m_cpuid.o: No such file or directory" Robert E Farrell
  • Re: [Valgrind-users] make dies: " /usr/bin/ar: libcoregrind_amd64_linux_a-m_cpuid.o: No such file or directory" João M. S. Silva
• [Valgrind-users] How to mark separate bits as undefined? juris
  • Re: [Valgrind-users] How to mark separate bits as undefined? Azat Khuzhin
  • Re: [Valgrind-users] How to mark separate bits as undefined? juris
  • Re: [Valgrind-users] How to mark separate bits as undefined? Florian Krohm
  • Re: [Valgrind-users] How to mark separate bits as undefined? John Reiser
• [Valgrind-users] Failed to read a valid object file image from memory. João M. S. Silva
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. Philippe Waroquiers
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. João M. S. Silva
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. Philippe Waroquiers
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. João M. S. Silva
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. Philippe Waroquiers
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. João M. S. Silva
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. Philippe Waroquiers
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. Matthias Schwarzott
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. João M. S. Silva
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. Philippe Waroquiers
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. João M. S. Silva
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. Philippe Waroquiers
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. João M. S. Silva
  • Re: [Valgrind-users] Failed to read a valid object file image from memory. João M. S. Silva
• [Valgrind-users] _mm_maskstore_ps issue Mark Abraham
  • Re: [Valgrind-users] _mm_maskstore_ps issue Mark Abraham
• [Valgrind-users] catchconv no usable output Donald Raikes
  • Re: [Valgrind-users] catchconv no usable output Philippe Waroquiers
• [Valgrind-users] memcheck GC: Increasing nodes, but constant survivors Paul Menzel
  • Re: [Valgrind-users] memcheck GC: Increasing nodes, but constant survivors Philippe Waroquiers
• [Valgrind-users] Problem wrapping C functions in C++ Andres Tiraboschi
• [Valgrind-users] valgrind: mmap(0x400000, 704512) failed in UME with error 22 (Invalid argument). Donald Raikes
  • Re: [Valgrind-users] valgrind: mmap(0x400000, 704512) failed in UME with error 22 (Invalid argument). Julian Seward
• [Valgrind-users] Query regarding valgrind build for Octeon MIPS 64 using cross compiler. MUHAMMADSAHEER C
  • Re: [Valgrind-users] Query regarding valgrind build for Octeon MIPS 64 using cross compiler. Maran Pakkirisamy
• [Valgrind-users] uninitialised value(s) - after explicit memset to 0 ?? David C. Rankin
  • Re: [Valgrind-users] uninitialised value(s) - after explicit memset to 0 ?? David Chapman
  • Re: [Valgrind-users] uninitialised value(s) - after explicit memset to 0 ?? David C. Rankin
• [Valgrind-users] Valgrind with linux daemon sankoor sampath
  • Re: [Valgrind-users] Valgrind with linux daemon John Reiser
  • Re: [Valgrind-users] Valgrind with linux daemon Philippe Waroquiers
• [Valgrind-users] A great trick for counting cycles using callgrind - but what about massif? Peter Toft
  • Re: [Valgrind-users] A great trick for counting cycles using callgrind - but what about massif? Josef Weidendorfer
• [Valgrind-users] Assertion 'DRD_(g_threadinfo)[tid].pt_threadid != INVALID_POSIX_THREADID' failed. Joe VanAndel
  • Re: [Valgrind-users] Assertion 'DRD_(g_threadinfo)[tid].pt_threadid != INVALID_POSIX_THREADID' failed. Bart Van Assche
• [Valgrind-users] ARM - WARNING: Serious error when reading debug info Raul Garcia
  • Re: [Valgrind-users] ARM - WARNING: Serious error when reading debug info Raul Garcia
  • Re: [Valgrind-users] ARM - WARNING: Serious error when reading debug info John Reiser
• [Valgrind-users] Helgrind: Recursive Locing of normal mutex SHEHAB ZAINELDINE
  • Re: [Valgrind-users] Helgrind: Recursive Locing of normal mutex Tom Hughes
  • Re: [Valgrind-users] Helgrind: Recursive Locing of normal mutex Tom Hughes
• [Valgrind-users] Error in callgrind ( ???:function ) Raul Garcia
  • Re: [Valgrind-users] Error in callgrind ( ???:function ) Josef Weidendorfer
  • Re: [Valgrind-users] Error in callgrind ( ???:function ) Azat Khuzhin
  • Re: [Valgrind-users] Error in callgrind ( ???:function ) Josef Weidendorfer
  • Re: [Valgrind-users] Error in callgrind ( ???:function ) Azat Khuzhin
  • Re: [Valgrind-users] Error in callgrind ( ???:function ) Josef Weidendorfer
  • Re: [Valgrind-users] Error in callgrind ( ???:function ) Azat Khuzhin
• [Valgrind-users] version number? Mark Roberts
  • Re: [Valgrind-users] version number? Tom Hughes
  • Re: [Valgrind-users] version number? Mark Roberts
  • Re: [Valgrind-users] version number? Tom Hughes
  • Re: [Valgrind-users] version number? Mark Roberts
  • Re: [Valgrind-users] version number? Tom Hughes
  • Re: [Valgrind-users] version number? Mark Roberts
• [Valgrind-users] Dump of opcode/mnemonic per code line Raul Garcia
  • Re: [Valgrind-users] Dump of opcode/mnemonic per code line Josef Weidendorfer
  • Re: [Valgrind-users] Dump of opcode/mnemonic per code line Raul Garcia
  • Re: [Valgrind-users] Dump of opcode/mnemonic per code line Josef Weidendorfer
• [Valgrind-users] problem running gdbserver_tests/nlvgdbsigqueue.vgtest Mark Roberts
  • Re: [Valgrind-users] problem running gdbserver_tests/nlvgdbsigqueue.vgtest Philippe Waroquiers
• Re: [Valgrind-users] Valgrind on Android Jelly Beans -- Can not launch app due to unrecognized instructions. Horatio
• [Valgrind-users] Fosdem 2015 talk slides online Mark Wielaard
• Re: [Valgrind-users] Enabling instrumentation with callgrind_control not working Christian Priebe
  • Re: [Valgrind-users] Enabling instrumentation with callgrind_control not working Philippe Waroquiers
  • Re: [Valgrind-users] Enabling instrumentation with callgrind_control not working Christian Priebe
  • Re: [Valgrind-users] Enabling instrumentation with callgrind_control not working Josef Weidendorfer
  • Re: [Valgrind-users] Enabling instrumentation with callgrind_control not working Christian Priebe
  • Re: [Valgrind-users] Enabling instrumentation with callgrind_control not working Josef Weidendorfer
  • Re: [Valgrind-users] Enabling instrumentation with callgrind_control not working Philippe Waroquiers
  • Re: [Valgrind-users] Enabling instrumentation with callgrind_control not working Christian Priebe
• [Valgrind-users] How to make use of callgrind --cacheuse=yes ? Stephen Kelly
  • Re: [Valgrind-users] How to make use of callgrind --cacheuse=yes ? Josef Weidendorfer
• [Valgrind-users] Enabling instrumentation with callgrind_control not working Christian Priebe
  • Re: [Valgrind-users] Enabling instrumentation with callgrind_control not working Josef Weidendorfer
• [Valgrind-users] Handling ioctl 0x30000001 in valgrind? Carl Ponder
  • [Valgrind-users] Handling ioctl 0x30000001 in valgrind? Carl Ponder
  • Re: [Valgrind-users] Handling ioctl 0x30000001 in valgrind? Tom Hughes
  • Re: [Valgrind-users] Handling ioctl 0x30000001 in valgrind? Carl Ponder
  • Re: [Valgrind-users] Handling ioctl 0x30000001 in valgrind? Julian Seward
  • Re: [Valgrind-users] Handling ioctl 0x30000001 in valgrind? Tom Hughes
  • Re: [Valgrind-users] Handling ioctl 0x30000001 in valgrind? Carl Ponder
  • Re: [Valgrind-users] Handling ioctl 0x30000001 in valgrind? Tom Hughes
  • Re: [Valgrind-users] Handling ioctl 0x30000001 in valgrind? Carl Ponder
  • Re: [Valgrind-users] Handling ioctl 0x30000001 in valgrind? Tom Hughes
  • Re: [Valgrind-users] Handling ioctl 0x30000001 in valgrind? Julian Seward
• [Valgrind-users] What is ioctl 0x30000001 kand...@illinois.edu
  • Re: [Valgrind-users] What is ioctl 0x30000001 Philippe Waroquiers
• [Valgrind-users] Is 0xC4 fixed in callgrind SVN version? Mikhail Kandel
  • Re: [Valgrind-users] Is 0xC4 fixed in callgrind SVN version? John Reiser
• [Valgrind-users] Help: Can't make Valgrind executable. Alan Balkany
  • Re: [Valgrind-users] Help: Can't make Valgrind executable. John Reiser
  • Re: [Valgrind-users] Help: Can't make Valgrind executable. Florian Krohm
  • Re: [Valgrind-users] Help: Can't make Valgrind executable. Azat Khuzhin
• [Valgrind-users] FOSDEM valgrind devroom schedule posted (Brussels, Saturday 31 Jan 2015) Mark Wielaard
• [Valgrind-users] Tool for tracing unmodified propagation of values? Christian Convey
• [Valgrind-users] Empty stack shown by Valgrind Austin Einter
  • Re: [Valgrind-users] Empty stack shown by Valgrind Philippe Waroquiers
  • Re: [Valgrind-users] Empty stack shown by Valgrind Tom Hughes
  • Re: [Valgrind-users] Empty stack shown by Valgrind Philippe Waroquiers
  • Re: [Valgrind-users] Empty stack shown by Valgrind John Reiser
  • Re: [Valgrind-users] Empty stack shown by Valgrind Austin Einter
• [Valgrind-users] suppress warning repetition João M. S. Silva
  • Re: [Valgrind-users] suppress warning repetition Tom Hughes
  • Re: [Valgrind-users] suppress warning repetition João M. S. Silva
  • Re: [Valgrind-users] suppress warning repetition David Goldsmith
  • Re: [Valgrind-users] suppress warning repetition João M. S. Silva
  • Re: [Valgrind-users] suppress warning repetition João M. S. Silva
  • Re: [Valgrind-users] suppress warning repetition João M. S. Silva
  • Re: [Valgrind-users] suppress warning repetition Tom Hughes
  • Re: [Valgrind-users] suppress warning repetition João M. S. Silva
  • Re: [Valgrind-users] suppress warning repetition John Reiser
  • Re: [Valgrind-users] suppress warning repetition João M. S. Silva
  • Re: [Valgrind-users] suppress warning repetition Ivo Raisr
  • Re: [Valgrind-users] suppress warning repetition Tom Hughes
  • Re: [Valgrind-users] suppress warning repetition João M. S. Silva
  • Re: [Valgrind-users] suppress warning repetition João M. S. Silva
  • Re: [Valgrind-users] suppress warning repetition Tom Hughes
  • Re: [Valgrind-users] suppress warning repetition Philippe Waroquiers
  • Re: [Valgrind-users] suppress warning repetition João M. S. Silva
  • Re: [Valgrind-users] suppress warning repetition David Chapman
  • Re: [Valgrind-users] suppress warning repetition João M. S. Silva
• [Valgrind-users] VALGRIND_DO_CLIENT_REQUEST Yakir Ben Senyur
  • Re: [Valgrind-users] VALGRIND_DO_CLIENT_REQUEST John Reiser
  • Re: [Valgrind-users] VALGRIND_DO_CLIENT_REQUEST Philippe Waroquiers
• [Valgrind-users] KCachegrind Wei Wen
  • Re: [Valgrind-users] KCachegrind Milian Wolff
  • Re: [Valgrind-users] KCachegrind Josef Weidendorfer
• [Valgrind-users] FOSDEM Valgrind dev-room - Brussels, 31 Jan 2015 - DEADLINE this weekend/Monday Mark Wielaard
• [Valgrind-users] Announcing heaptrack - A heap memory profiler for Linux Milian Wolff
• [Valgrind-users] source file location João M. S. Silva
  • Re: [Valgrind-users] source file location Tom Hughes
  • Re: [Valgrind-users] source file location João M. S. Silva
  • Re: [Valgrind-users] source file location Tom Hughes

• Earlier messages
• Later messages