|
From: Chuck B. <cb...@vi...> - 2004-05-11 18:41:49
|
Has anyone been able to successfully run valgrind on FC2? I've tried versions 2.0.0, 2.1.0, 2.1.1 and cvs and while it builds without complaint (well it does complain about xorg versus xfree but that's benign). When I run valgrind it will either segfault or give the following error: error while loading shared libraries: /usr/lib/valgrind/valgrind.so: undefined symbol: __libc_accept (or __libc_connect) Any thoughts would be appreciated. -- Chuck |
|
From: Chuck B. <cb...@vi...> - 2004-05-21 16:52:42
|
Chuck Byam wrote: > Has anyone been able to successfully run valgrind on FC2? I've tried > versions 2.0.0, 2.1.0, 2.1.1 and cvs and while it builds without > complaint (well it does complain about xorg versus xfree but that's > benign). When I run valgrind it will either segfault or give the > following error: > > error while loading shared libraries: /usr/lib/valgrind/valgrind.so: > undefined symbol: __libc_accept (or __libc_connect) > > Any thoughts would be appreciated. > -- > Chuck > While trying to research this I was pointed to the following link: http://sources.redhat.com/ml/libc-hacker/2004-05/msg00001.html Which indeed would explain the undefined symbol references. It's apparent that valgrind is making internal functions calls to libc. Is there any plan to move away from this practice? Thanks, CB |