Thanks a bunch for trying it out John.
I have valgrind 3.5.0, and LD_LIBRARY_PATH points to /usr/local/lib, which is
where log4cxx libs are. That's all I can think of in the env. Different from
yours, mine is not 64-bit Fedora. Are your gcc etc. versions the same?
Wonder where I should look?
Here's ldd output:
libapr-1.so.0 => /usr/local/lib/libapr-1.so.0 (0x0080e000)
libaprutil-1.so.0 => /usr/local/lib/libaprutil-1.so.0 (0x002c4000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x006e6000)
libc.so.6 => /lib/libc.so.6 (0x00347000)
libdl.so.2 => /lib/libdl.so.2 (0x004f0000)
libexpat.so.1 => /lib/libexpat.so.1 (0x00c73000)
libfreebl3.so => /lib/libfreebl3.so (0x008ce000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00533000)
/lib/ld-linux.so.2 (0x00326000)
liblog4cxx.so.10 => /usr/local/lib/liblog4cxx.so.10 (0x00110000)
libm.so.6 => /lib/libm.so.6 (0x004fe000)
libpthread.so.0 => /lib/libpthread.so.0 (0x004d3000)
librt.so.1 => /lib/librt.so.1 (0x00569000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x05046000)
libuuid.so.1 => /lib/libuuid.so.1 (0x004f7000)
linux-gate.so.1 => (0x00ec8000)
-----Original Message-----
From: John Reiser [mailto:[email protected]]
Sent: Wed 4/20/2011 3:04 PM
To: [email protected]
Subject: Re: [Valgrind-users] Valgrind errors with log4cxx
> I am on Fedora Core 14, kernel 2.6.35.12-88, g++ 4.5.1, glibc-2.13.1.
> int main(const int argc,
> const char** argv)
> {
> return (0);
> }
> g++ -g -Wall -o Test.o -c Test.cpp ### Note no "src/"
> g++ -g Test.o -o test -llog4cxx
It works for me on Fedora 14:
gcc-c++-4.5.1-4.fc14.x86_64
glibc-2.13-1.x86_64
kernel-2.6.35.12-88.fc14.x86_64
$ ldd ./test | sort
/lib64/ld-linux-x86-64.so.2 (0x0000003d25a00000)
libapr-1.so.0 => /usr/lib64/libapr-1.so.0 (0x00007fdfd804c000)
libaprutil-1.so.0 => /usr/lib64/libaprutil-1.so.0 (0x00007fdfd8279000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00000037af000000)
libc.so.6 => /lib64/libc.so.6 (0x0000003d25e00000)
libdb-4.8.so => /lib64/libdb-4.8.so (0x0000003d37200000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003d26600000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x0000003d2a200000)
libfreebl3.so => /lib64/libfreebl3.so (0x00000037aec00000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003d27600000)
liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x0000003114000000)
libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x0000003113c00000)
liblog4cxx.so.10 => /usr/lib64/liblog4cxx.so.10 (0x00007fdfd849f000)
libm.so.6 => /lib64/libm.so.6 (0x0000003d26e00000)
libnspr4.so => /lib64/libnspr4.so (0x0000003d34a00000)
libnss3.so => /usr/lib64/libnss3.so (0x0000003113000000)
libnssutil3.so => /usr/lib64/libnssutil3.so (0x0000003d33600000)
libplc4.so => /lib64/libplc4.so (0x0000003d33200000)
libplds4.so => /lib64/libplds4.so (0x0000003d32e00000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003d26200000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003d28a00000)
libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00000037b0000000)
libsmime3.so => /usr/lib64/libsmime3.so (0x0000003113800000)
libssl3.so => /usr/lib64/libssl3.so (0x0000003113400000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003d32200000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x0000003d31200000)
libz.so.1 => /lib64/libz.so.1 (0x0000003d27200000)
linux-vdso.so.1 => (0x00007fff9d5be000)
$ valgrind ./test
==3413== Memcheck, a memory error detector
==3413== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==3413== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==3413== Command: ./test
==3413==
==3413==
==3413== HEAP SUMMARY:
==3413== in use at exit: 0 bytes in 0 blocks
==3413== total heap usage: 987 allocs, 987 frees, 39,592 bytes allocated
==3413==
==3413== All heap blocks were freed -- no leaks are possible
==3413==
==3413== For counts of detected and suppressed errors, rerun with: -v
==3413== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6 from 6)
$
--
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
