|
From: <Woe...@on...> - 2003-12-30 11:56:24
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, when is Valgrind's libpthread.so used? I've two applications linked against libqt-mt.so and so against libpthread.so. If I start the apps with valgrind -v app 1 reports =2E.. =3D=3D8915=3D=3D Reading syms from /usr/lib/valgrind/libpthread.so =2E.. =3D=3D8915=3D=3D REPLACING libc(__errno_location) with libpthread(__errno_l= ocation) =3D=3D8915=3D=3D REPLACING libc(__h_errno_location) with libpthread(__h_err= no_location) =3D=3D8915=3D=3D REPLACING libc(__res_state) with libpthread(__res_state) =3D=3D8915=3D=3D =3D=3D8915=3D=3D TRANSLATE: 0x40E1EFA0 redirected to 0x40CFE4A5 =2E.. and app 2 reports =2E.. =3D=3D9074=3D=3D Reading syms from /lib/libpthread-0.10.so =2E.. and a lot of invalid read/write of size 4 which make the report useless. I'm using Debian's sid (Valgrind 2.1.0) but have the same effect on SuSE 9.0 (Valgrind-20031012). How can I convince Valgrind to use its own libpthread.so? Andr=E9 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/8WfoGcp/AjG8ndYRAvwDAJ9m6s+oF1pac8mXF4cgTG/WXAfGdgCbBvlb erT+KonQ133g4Gxa7tH8edE=3D =3Dq1D4 =2D----END PGP SIGNATURE----- |
|
From: Dirk M. <dm...@gm...> - 2003-12-30 15:36:30
|
On Tuesday 30 December 2003 12:56, Andr=E9 W=F6bbeking wrote:
> =3D=3D9074=3D=3D Reading syms from /lib/libpthread-0.10.so
well, app two is linked against libpthread-0.10 then and not against=20
libpthread, right?
valgrind isn't smart enough to detect that. try adding a symlink in=20
${prefix}/lib/valgrind to its libpthread.so
Dirk
|
|
From: <Woe...@on...> - 2003-12-30 16:31:23
|
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Dirk,
On Tuesday 30 December 2003 16:27, Dirk Mueller wrote:
> On Tuesday 30 December 2003 12:56, Andr=E9 W=F6bbeking wrote:
> > =3D=3D9074=3D=3D Reading syms from /lib/libpthread-0.10.so
>
> well, app two is linked against libpthread-0.10 then and not against
> libpthread, right?
If it would be that easy. Both apps are linked=20
against /lib/libpthread.so.0 which is a link=20
to /lib/libpthread-0.10.so.
> valgrind isn't smart enough to detect that. try adding a symlink in
> ${prefix}/lib/valgrind to its libpthread.so
there is a link libpthread.so.0 to Valgrind's libpthread.so. A new link=20
from libpthread-0.10.so to Valgrind's libpthread.so doesn't help.
Andr=E9
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/8ahdGcp/AjG8ndYRAhF/AJ9sQk7NBoNkUYGTU1NTo8uAeaQzkwCggx7Z
HLUaAXhOtfdZtl79GVyuh24=3D
=3D1wc5
=2D----END PGP SIGNATURE-----
|
|
From: <Woe...@on...> - 2003-12-31 10:38:01
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 30 December 2003 12:56, Andr=E9 W=F6bbeking wrote: > Hi, > > when is Valgrind's libpthread.so used? I've two applications linked > against libqt-mt.so and so against libpthread.so. If I start the apps > with valgrind -v app 1 reports > > ... > =3D=3D8915=3D=3D Reading syms from /usr/lib/valgrind/libpthread.so > > and app 2 reports > > ... > =3D=3D9074=3D=3D Reading syms from /lib/libpthread-0.10.so > ... > and a lot of invalid read/write of size 4 which make the report > useless. I found the problem. The build enviroment was broken. It linked with=20 =2D -Wl,-rpath,/lib -L/lib. So Valgrind's libpthread couldn't be used. Andr=E9 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/8qb+Gcp/AjG8ndYRAqpiAJ9KNs/UDbIHuyJTAzgeN8d+eMkeyACfdj+x vYQUMvA0Y/gC0AWnoxA/bVQ=3D =3DCtVC =2D----END PGP SIGNATURE----- |