-
Notifications
You must be signed in to change notification settings - Fork 571
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
i#5879: Added an example analyzer #5916
base: master
Are you sure you want to change the base?
i#5879: Added an example analyzer #5916
Conversation
I am seeing linking errors when I try to use these functions. It works if I extract the linker cmd line and manually add libdynamorio.so, but I wasn't able to figure out what I needed to add in my cmake script.
|
Nevermind, I was missing drdecode |
Seeing this error. Works if I point LD_LIBRARY_PATH to the lib64/release dir
|
Windows build is failing due to symbols being defined in both libucrtd.lib and dynamorio.dll
|
I remember various problems like this going away with the right ordering of libraries on the link line: probably there are mentions of ordering in the cmake code like:
I thought that static libc list included libucrt? And adds the d for debug build? |
Any idea how to fix this? |
…-to-create-new-analysis-tools
x86-32 failure looks like #5908 |
Missing the cmake call which adds the lib path to the ELF file? If legacy traces don't need support drdecode is probably all that's needed and not full libdynamorio in an analyzer. |
I added these statements so the cmake script is not explicitly adding libdynamorio. Should I explicitly add lib64/release to RPATH?
|
Issue: #5879