|
From: Christopher S. <csw...@sy...> - 2010-03-12 18:10:01
|
Julian Seward <jseward <at> acm.org> writes: > > On Friday 12 March 2010, Christopher Swanson wrote: > > John Reiser <jreiser <at> bitwagon.com> writes: > > > > valgrind: A must-be-redirected function > > > > valgrind: whose name matches the pattern: strlen > > > > valgrind: in an object with soname matching: ld-linux-x86-64.so.2 > > > > valgrind: was not found whilst processing > > > > valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 > > > 1) Figure out a way to include the strlen call into dl-allobjs.os, or > > 2) Patch the makefile to add the strlen.os to the librtld.mk file. > > Sorry, this fell through the cracks. The standard solution to these > problems is simply to ask your package manager to install the debuginfo > package (containing the required symbols) for glibc. I'm not sure > what the package name is on Fedora. I'd guess it would match > "*libc*debuginfo*" or at least "*libc*debug*". Can you find anything > like that? > > J > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > Thanks Julian, In this case, I am the package manager and I am unfamiliar on the compile options to define to create the debuginfo information. I tried '-g' in CFLAGS and that does enable gdb to trace the libc functions. However, valgrind seems to want a different reference type. I am following John Reiser's suggestion to include strlen in ld.so. |