On 04/08/2014 12:18 PM, Sebastian Banescu wrote:
> Hi,
>
> I've encountered the following error while running the retee.C sample
> application given in Appendix A of the DyninstAPI manual:
>
> Attaching to process 2232...
> --SERIOUS-- #0: Dyninst was unable to load the dyninst runtime library
> into the application. This may be caused by statically linked
> executables, or by having dyninst linked against a different version of
> libelf than it was built with.
> --FATAL-- #68: Dyninst was unable to attach to the specified process
> --FATAL-- #68: src\BPatch.C[1040]: no process 2232 defined in procsByPid
>
> This error seems to have also been encountered on RHL a few months ago
> according to this bug post:
> https://bugzilla.redhat.com/show_bug.cgi?id=1005892
Can you try with the debug flags set in the environment, as suggested in
that bug's comment #4?
> My host OS is: Win 7 32-bit
I'd be surprised if such different a platform faced the exact same bug,
but if so, that might help identify the root cause.
Thanks,
Josh
|