Nice thought, but no.
These are the only clues (not much):
Code:
31380: relocation processing: /usr/lib/libenvload.so (lazy)
31380: symbol=__gmon_start__; lookup in file=./libc.so.6 [0]
31380: symbol=__gmon_start__; lookup in file=/usr/lib/libenvload.so [0]
31380: symbol=__gmon_start__; lookup in file=/mnt/us/extensions/system/lib/ld-linux-armhf.so.3 [0]
31380: symbol=_Jv_RegisterClasses; lookup in file=./libc.so.6 [0]
31380: symbol=_Jv_RegisterClasses; lookup in file=/usr/lib/libenvload.so [0]
31380: symbol=_Jv_RegisterClasses; lookup in file=/mnt/us/extensions/system/lib/ld-linux-armhf.so.3 [0]
31380: symbol=__cxa_finalize; lookup in file=./libc.so.6 [0]
31380: binding file /usr/lib/libenvload.so [0] to ./libc.so.6 [0]: normal symbol `__cxa_finalize' [GLIBC_2.4]
Any "what provides" query I can come up with has not helped.
Might be something that hooks the loader's audit interface.
And if nothing else help, then I'll: objdump -d /usr/lib/libenvload.so on the turkey.
