|
From: Scott M. <sm...@no...> - 2005-03-23 19:23:58
|
Thx, that gives us some things to try! As an update, it's starting to look like the reason valgrind is using the wrong libpthread is related to rtldi. Are there any known Valgrind workarounds involving libs set by rtldi? Thx again all, Scott. -----Original Message----- From: Paul Pluzhnikov [mailto:ppl...@gm...] Sent: Tuesday, March 22, 2005 8:31 PM To: Mills, Scott [CAR:2V62:EXCH] Cc: val...@li...; Jeremy Fitzhardinge Subject: Re: [Valgrind-users] RE: Question about valgrind's libpthread On Tue, 22 Mar 2005 15:56:04 -0800, Jeremy Fitzhardinge <je...@go...> wrote: > Scott Mills wrote: > > > Before we get a chance to upgrade (we're still running < 2.2.0), is > > there anyway I can 'unset' -rpath without rebuilding the target > > program? > > I don't think so; it's embedded in the .so files you generate. There sure is: load the exe/DSO into emacs, invoke hexl-mode, edit rpath away (replacing the first character of the string with NUL character should do the trick). Cheers, |