From: David C. <dc...@gm...> - 2014-01-26 02:20:24
|
Hi, I've got an issue with memcheck in Valgrind 3.8.1 hanging. I've left processes running for weeks or even months but they don't complete (normally these processes run in a few minutes tops, and they were working fine with memcheck until a while ago. Has anyone seen anything like this before? Here are the details: options: --quiet --track-origins=yes --free-fill=7a --child-silent-after-fork=yes --fair-sched=no --log-file=/path/to/log --suppressions=/path/to/suppression.file strace shows: Process 5223 attached - interrupt to quit read(1027, system details: $ uname -a Linux HOSTNAME 2.6.18-194.3.1.el5 #1 SMP Sun May 2 04:17:42 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.5 (Tikanga) Top shows: 732 USER 25 0 2396m 1.6g 110m S 99.8 3.5 86263:19 memcheck-amd64- 25100 USER 25 0 2498m 1.7g 112m S 99.8 3.6 86272:55 memcheck-amd64- Ps shows pipe wait in WCHAN: 0 S nbezj7v 25100 1864 98 85 0 - 639685 pipe_w 2013 ? 59-22:03:14 /path/to/valgrind options Have seen it also hang on fast mutexes – i.e. strace/ps will show the process in FUTEX_WAIT status. Thanks, David. |