-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to run drmemory v2.5.0 on RHEL 8.2 #2453
Comments
Maybe the bin64 version works better.
Looks like the stack is hosed. |
RHEL 8.2 is a bit better
and it works OK with LD_LIBRARY_PATH pointing to libunwind.so |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I downloaded Dr. Memory v2.5..0 from https://github.com/DynamoRIO/drmemory/releases/download/release_2.5.0/DrMemory-Linux-2.5.0.tar.gz
Extracted & set the environment variables properly.
When I tried to run my app using command: "drmemory -- myapp myapp_args"
I got this error: "drmemory: No such file or directory"
so I tried to do ldd & got this error:
ldd drmemory
not a dynamic executable
Next, I tried running readelf and got below output:
readelf -d drmemory
Dynamic section at offset 0xafd3c contains 31 entries:
Tag Type Name/Value
0x00000001 (NEEDED) Shared library: [libdynamorio.so]
0x00000001 (NEEDED) Shared library: [libgcc_s.so.1]
0x00000001 (NEEDED) Shared library: [libc.so.6]
0x0000001d (RUNPATH) Library runpath: [$ORIGIN/../dynamorio/lib32/release:$ORIGIN/../dynamorio/lib32]
0x0000000c (INIT) 0x1a000
0x0000000d (FINI) 0x4c0b8
0x00000019 (INIT_ARRAY) 0x76b78
0x0000001b (INIT_ARRAYSZ) 4 (bytes)
0x0000001a (FINI_ARRAY) 0x76b7c
0x0000001c (FINI_ARRAYSZ) 4 (bytes)
0x00000004 (HASH) 0x1ec
0x6ffffef5 (GNU_HASH) 0xd34
0x00000005 (STRTAB) 0x34b8
0x00000006 (SYMTAB) 0x1828
0x0000000a (STRSZ) 8119 (bytes)
0x0000000b (SYMENT) 16 (bytes)
0x00000015 (DEBUG) 0x0
0x00000003 (PLTGOT) 0xb0e54
0x00000002 (PLTRELSZ) 624 (bytes)
0x00000014 (PLTREL) REL
0x00000017 (JMPREL) 0x1943c
0x00000011 (REL) 0x58a4
0x00000012 (RELSZ) 80792 (bytes)
0x00000013 (RELENT) 8 (bytes)
0x0000001e (FLAGS) BIND_NOW
0x6ffffffb (FLAGS_1) Flags: NOW PIE
0x6ffffffe (VERNEED) 0x5804
0x6fffffff (VERNEEDNUM) 2
0x6ffffff0 (VERSYM) 0x5470
0x6ffffffa (RELCOUNT) 10093
0x00000000 (NULL) 0x0
The same drmemory v2.5.0 is working fine on windows platform.
So wondering: Is Dr. Memory ever tested on Red Hat platform?
Any workaround or solution to this would help.
Thanks in advance.
The text was updated successfully, but these errors were encountered: