Richard Levitte <levitte@xxxxxxxxxxx> wrote:
>> Running LDD on the binaries in test/* shows that they appear to link against
>> the "system" copies of libssl and libcrypto.
>>
>> Perhaps something I'm missing is setting up LD_PRELOAD or some such so that
>> the tests run the local copy of libssl/libcrypto, but I can't find that.
>> Am I missing something?
>>
>> This is, I think, making it very difficult for me to bisect a problem.
>>
>> It seems to me that the test cases ought to be statically linked to make
>> it easiest to know what code they are running. (This also makes it slightly
>> easier to use gdb on them)
> There's a script called util/shlib_wrap.sh that you place first on the
> command line:
> ./util/shlib_wrap.sh test/whatevertest
> ./util/shlib_wrap.sh ldd test/whatevertest
> ./util/shlib_wrap.sh gdb test/whatevertest
And another email says that this is done by default for "make test".
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@xxxxxxxxxxxx http://www.sandelman.ca/ | ruby on rails [
Attachment:
signature.asc
Description: PGP signature
