|
From: James A. <jam...@me...> - 2004-09-03 20:53:19
|
hey,
i posted a little while back about newer versions of valgrind running very
slowly. i'm still having that problem (with 2.2.0, on red hat 7.3), and i have
some strace info to go with it. seems that my program gets hung up in all sorts
of crazy read calls (note the repeated (resource temporarily unavailable). the
program was useable under valgrind 2.0.0. pretty unuseable at this point.
rt_sigprocmask(SIG_SETMASK, NULL, ~[ILL BUS FPE KILL SEGV STOP], 8) = 0
rt_sigprocmask(SIG_SETMASK, ~[], ~[ILL BUS FPE KILL SEGV STOP], 8) = 0
rt_sigtimedwait(~[ILL BUS FPE KILL SEGV STOP], 0xbfffe9d4) = -1 EAGAIN (Resource
temporarily unavailable)
rt_sigprocmask(SIG_SETMASK, ~[ILL BUS FPE KILL SEGV STOP], NULL, 8) = 0
SYS_224(0xbfffea50, 0xb002f0a3, 0x101bc, 0xb003067f) = 4960
read(826, "\1\0\0\0\1\0\0\0\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 136) = 13
6
read(826, "\2\0\0\0\1\0\0\0\216\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 136) = 13
6
read(826, "\3\0\0\0\1\0\0\0\216\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 136) = 13
6
read(826, 0xbfffe9b4, 136) = -1 EAGAIN (Resource temporarily unavai
lable)
gettimeofday({1094241990, 946626}, NULL) = 0
write(829, "\1\0\0\0\10\0\0\0\30\347\32\260", 12) = 12
SYS_224(0xbfffea68, 0xb0032961, 0xbfffe9e4, 0xb0046f6d) = 4960
SYS_224(0xbfffe9c0, 0xb00306b3, 0x2, 0xb01adfc4) = 4960
rt_sigprocmask(SIG_SETMASK, NULL, ~[ILL BUS FPE KILL SEGV STOP], 8) = 0
rt_sigprocmask(SIG_SETMASK, ~[], ~[ILL BUS FPE KILL SEGV STOP], 8) = 0
rt_sigtimedwait(~[ILL BUS FPE KILL SEGV STOP], 0xbfffe9d4) = -1 EAGAIN (Resource
temporarily unavailable)
rt_sigprocmask(SIG_SETMASK, ~[ILL BUS FPE KILL SEGV STOP], NULL, 8) = 0
SYS_224(0xbfffea50, 0xb002f0a3, 0x101bc, 0xb003067f) = 4960
read(826, 0xbfffe9b4, 136) = -1 EAGAIN (Resource temporarily unavai
lable)
gettimeofday({1094241990, 947237}, NULL) = 0
write(831, "\1\0\0\0\10\0\0\0\304\352\32\260", 12) = 12
SYS_224(0xbfffea68, 0xb0032961, 0xbfffe9e4, 0xb0046f6d) = 4960
SYS_224(0xbfffe9c0, 0xb00306b3, 0x3, 0xb01adfc4) = 4960
rt_sigprocmask(SIG_SETMASK, NULL, ~[ILL BUS FPE KILL SEGV STOP], 8) = 0
rt_sigprocmask(SIG_SETMASK, ~[], ~[ILL BUS FPE KILL SEGV STOP], 8) = 0
rt_sigtimedwait(~[ILL BUS FPE KILL SEGV STOP], 0xbfffe9d4) = -1 EAGAIN (Resource
temporarily unavailable)
rt_sigprocmask(SIG_SETMASK, ~[ILL BUS FPE KILL SEGV STOP], NULL, 8) = 0
SYS_224(0xbfffea50, 0xb002f0a3, 0x101bc, 0xb003067f) = 4960
read(826, 0xbfffe9b4, 136) = -1 EAGAIN (Resource temporarily unavai
lable)
write(825, "\1\0\0\0\f\0\0\0l\343\32\260", 12) = 12
SYS_224(0xbfffea68, 0xb0032961, 0xbfffe9e4, 0xb0046f6d) = 4960
SYS_224(0xbfffe9c0, 0xb00306b3, 0x1, 0xb01adfc4) = 4960
rt_sigprocmask(SIG_SETMASK, NULL, ~[ILL BUS FPE KILL SEGV STOP], 8) = 0
rt_sigprocmask(SIG_SETMASK, ~[], ~[ILL BUS FPE KILL SEGV STOP], 8) = 0
rt_sigtimedwait(~[ILL BUS FPE KILL SEGV STOP], 0xbfffe9d4) = -1 EAGAIN (Resource
temporarily unavailable)
rt_sigprocmask(SIG_SETMASK, ~[ILL BUS FPE KILL SEGV STOP], NULL, 8) = 0
SYS_224(0xbfffea50, 0xb002f0a3, 0x101bc, 0xb003067f) = 4960
read(826, "\1\0\0\0\1\0\0\0\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 136) = 13
6
read(826, 0xbfffe9b4, 136) = -1 EAGAIN (Resource temporarily unavai
lable)
write(825, "\1\0\0\0 \0\0\0l\343\32\260", 12) = 12
|
|
From: Tom H. <th...@cy...> - 2004-09-03 21:37:34
|
In message <loo...@po...>
James Ahlborn <jam...@me...> wrote:
> i posted a little while back about newer versions of valgrind running very
> slowly. i'm still having that problem (with 2.2.0, on red hat 7.3), and i
> have some strace info to go with it. seems that my program gets hung up in
> all sorts of crazy read calls (note the repeated (resource temporarily
> unavailable). the program was useable under valgrind 2.0.0. pretty
> unuseable at this point.
Those reads aren't crazy, they're just valgrind's main thread
checking for events from the proxy LWP that handles signals and
blocking system calls. It's entirely normal to see those.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: James A. <jam...@me...> - 2004-09-04 01:17:31
|
> Tom Hughes <thh <at> cyberscience.com> writes: > Those reads aren't crazy, .... So, any ideas why my program would be running so slow? Any ideas on how to diagnose it? -james |