|
From: Konstantin S. <kon...@gm...> - 2009-01-20 13:29:21
|
Hello, I am experiencing a problem with valgrind: the memcheck process becomes zombie at the very end of the program execution. This happens with the fresh valgrind trunk. I run valgrind -v --trace-syscalls=yes my_program and it hangs one out of 5-10 runs. 'top' shows: 7806 me 18 0 0 0 0 Z 0 0.0 0:16.27 memcheck <defunct> The last lines printed by valgrind before it hangs are: SYSCALL[7806,4]( 9) sys_mmap ( 0x0, 69632, 7, 98, -1, 0 ) --> [pre-success] Success(0xbb6b000) SYSCALL[7806,4]( 10) sys_mprotect ( 0xbb6b000, 4096, 0 )[sync] --> Success(0x0) SYSCALL[7806,4]( 56) sys_clone ( 3d0f00, 0xbb7a1d0, 0xbb7b9f0, 0xbb7b9f0, 0xbb7b960 ) --> [pre-success] Success(0x1f93) SYSCALL[7806,4]( 96) sys_gettimeofday ( 0xb75bd70, 0x0 )[sync] --> Success(0x0) SYSCALL[7806,4]( 96) sys_gettimeofday ( 0xb75bac0, 0x0 )[sync] --> Success(0x0) SYSCALL[7806,4]( 96) sys_gettimeofday ( 0xb75bd70, 0x0 )[sync] --> Success(0x0) SYSCALL[7806,4]( 96) sys_gettimeofday ( 0xb75bac0, 0x0 )[sync] --> Success(0x0) SYSCALL[7806,4](202) sys_futex ( 0x8427820, 0, 0, 0xb75bb20, 0x8427820 ) --> [async] ... SYSCALL[7806,4](202) ... [async] --> Failure(0x6e) SYSCALL[7806,4]( 96) sys_gettimeofday ( 0xb75bac0, 0x0 )[sync] --> Success(0x0) SYSCALL[7806,4]( 96) sys_gettimeofday ( 0xb75bd70, 0x0 )[sync] --> Success(0x0) SYSCALL[7806,4]( 96) sys_gettimeofday ( 0xb75bac0, 0x0 )[sync] --> Success(0x0) SYSCALL[7806,4](202) sys_futex ( 0x8427820, 0, 0, 0xb75bb20, 0x8427820 ) --> [async] ... SYSCALL[7806,1]( 11) sys_munmap ( 0x8437000, 8192 )[sync] --> Success(0x0) SYSCALL[7806,1](231) exit_group( 0 ) --> [pre-success] Success(0x0) SYSCALL[7806,5](186) sys_gettid ()[sync] --> Success(0x1f93) SYSCALL[7806,5](202) sys_futex ( 0x8427f20, 0, 0, 0x0, 0x8427f20 ) --> [async] ... SYSCALL[7806,4](202) ... [async] --> Failure(0x6e) If valgrind passes, it does not print lines containing "Failure(0x6e)" Any idea how to attack this problem further? Thanks, --kcc |