Closed mcgrady1 closed 2 years ago
Sorry for the slow response. This isn't my code to be providing support for, but I guess someone's gotta do it.
The file that's failing to open is the actual trace log, it is created by a qemu subprocess. The tracer code launches a special build of qemu that has some caching options disabled in order to get an accurate trace. If we can't open it here, it's because qemu failed to write that file there. There are several reasons why this could be:
/dev/shm
(very fast ram-mounted temporary filesystem)I can't debug this problem for you with the limited information given, so you'll need to debug it on your own. clone the repo and add some print statements to dump out the exact qemu command that gets called, then try running it on your own and see where it dies.
The args of Popen is " ['/usr/bin/x86_64', '-d', 'exec', '-D', '/dev/shm/tracer-log-AnE0Ca', './test1_gcc'] ". But the command "/usr/bin/x86_64" has no paramter -d. Can you give us some detail tutorial of DRILLER?
You have installed tracer and shellphish_qemu globally, as root. This is highly not recommended.
We'll fix this eventually, but for now the fix is "use a virtualenv".
But I have no authority when I install "shellphish_qemu" and "tracer " with normal user.
You should have authority if you use a virtual environment
Could you give us some more detial tutorials and examples of driller?
This issue has been marked as stale
because it has no recent activity. Please comment or add the pinned
tag to prevent this issue from being closed.
This issue has been closed due to inactivity.