|
From: Scott M. <sm...@no...> - 2005-03-22 17:48:40
|
Resending, as first attempt didn't seem to go through... Scott. -----Original Message----- From: Mills, Scott [CAR:2V62:EXCH] Sent: Tuesday, March 22, 2005 10:31 AM To: val...@li... Subject: Question about valgrind's libpthread Hi, Still new to valgrind, so I some high level questions. I've noticed that when we run Valgrind on process Foo in environment A, it will pickup Valgrind's libpthread library properly. In a different environment B, when running Valgrind on process Foo, it ignored Valgrind's libpthread and only uses /lib/libpthread.so instead. The same version of Valgrind is run in both environments. I don't have a lot of knowledge about Foo, but my guess is that this problem is occurring because of how Foo was built/compiled in the two environments. I found some information online: http://sourceforge.net/mailarchive/forum.php?forum_id=32038&max_rows=25&styl e=nested&viewmonth=200312 which seems to suggest that the flags - -Wl,-rpath,/lib -L/lib were used when being built which somehow prevented Valgrind from using it's own libpthread. Can anyone confirm/deny my suspicions and provide insight on what the - -Wl,-rpath,/lib -L/lib flags are and how they are used? Thx for any help, Scott. |
|
From: Jeremy F. <je...@go...> - 2005-03-22 18:10:58
|
Scott Mills wrote:
> Can anyone confirm/deny my suspicions and provide insight on what the
> - -Wl,-rpath,/lib -L/lib flags are and how they are used?
>
-rpath sets the runtime linkers search path, and it takes precident over
all other path settings, including LD_LIBRARY_PATH (which is what
Valgrind 2.2.0 relies on to substitute its own libpthread).
This is all moot now, since Valgrind 2.4.0 doesn't have its own
libpthread anymore, in faviour of using the system libpthread.
J
|