|
From: Farid A. <far...@ho...> - 2005-06-13 18:03:17
|
(I apologize for previous email: hotmail defaults to rich text mode) Hi, I recently switched from valgrind 2.0.0 to valgrind 2.4.0. when I started valgrind with the following options: valgrind --skin=none --trace-syscalls=yes -v MyProgram valgrind worked fine in version 2.0.0 but loading the dynamic libraries at startup takes a long long time to load in verion 2.4.0 (some dynamic libraries took around 4 minutes each to load. Also system calls which did not show in 2.0.0 are now showing in 2.4.0. For example in Valgrind 2.0.0 I will get ==8927== Reading syms from /sanbox/foo.so but in Valgrind 2.4.0 I will get something like the following and then a long pause for most dynamic libraries --> 985698304 (0x3AC09000) SYSCALL[8287,1](125):sys_mprotect ( 0x3AC20000, 13224, 0 ) --> 0 (0x0) SYSCALL[8287,1]( 90) special:old_mmap ( 0x3AC20000, 16384, 3, 18, 3, 90112 ) --> 985792512 (0x3AC20000) SYSCALL[8287,1]( 6):sys_close ( 3 ) --> 0 (0x0) SYSCALL[8287,1]( 5) mayBlock:sys_open ( 0xAFEFD4BC(/sandbox/foo.so), 0 ) --> ... SYSCALL[8287,1]( 5) --> 3 (0x3) SYSCALL[8287,1]( 3) mayBlock:sys_read ( 3, 0xAFEFD694, 1024 ) --> ... SYSCALL[8287,1]( 3) --> 1024 (0x400) SYSCALL[8287,1](197):sys_fstat64 ( 3, 0xAFEFD5C4 ) --> 0 (0x0) SYSCALL[8287,1]( 90) special:old_mmap ( 0x0, 4096, 3, 34, -1, 0 ) --> 985812992 (0x3AC25000) SYSCALL[8287,1]( 90) special:old_mmap ( 0x0, 77212, 5, 2, 3, 0 )==8287== Reading syms from /sandbox/foo.so (0x3AC27000) --> 985821184 (0x3AC27000) What could be wrong? Thanks Farid |
|
From: Nicholas N. <nj...@cs...> - 2005-07-19 03:47:10
|
On Mon, 13 Jun 2005, Farid Abizeid wrote: > Hi, > I recently switched from valgrind 2.0.0 to valgrind 2.4.0. > > when I started valgrind with the following options: > valgrind --skin=none --trace-syscalls=yes -v MyProgram > > valgrind worked fine in version 2.0.0 but loading the dynamic libraries at > startup takes a long long time to load in verion 2.4.0 (some dynamic > libraries took around 4 minutes each to load. Also system calls which did not > show in 2.0.0 are now showing in 2.4.0. Do you know if the shared objects have debugging information in the stabs format? If so, this could be the problem described in bug #109040 (http://bugs.kde.org/show_bug.cgi?id=109040). N |