-
Notifications
You must be signed in to change notification settings - Fork 601
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
can't run in docker #2387
Comments
(added some info as edit in github) |
What version of docker is this? |
Thank you !
I tried to debug and it seems the num_bytes arg is becoming a negative number in process_execve but not sure what it means |
My guess would be that the Can you run it again with RR_LOG=debug in the environment and put that somewhere? |
ok, but .. where does this log to? |
RR_LOG_FILE=log produces an empty file |
sorry, didn't think of combining it:
|
,
…On 17 Sep 2019 16:47, "Kyle Huey" ***@***.***> wrote:
My guess would be that the /proc filesystem inside the container is not
available for some reason, and that we're dying trying to record values
from the /proc/<pid>/mem of the tracee (ls in this case).
Can you run it again with RR_LOG=debug in the environment and put that
somewhere?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2387>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGKZ63WGCFORUOAOSOERZDQKDNWRANCNFSM4IXNA52A>
.
|
Can you attach gdb to rr itself (not to the tracee with the printed instructions) and get a stack trace? |
using pidof ?
|
i am not sure if this is the stacktrace sorry, is there another way to attach except attach pid (i guess you can't directly rr under rr ) |
(on the other hand, am i correct that if one somehow runs |
This is the right stacktrace and it's helpful, thanks. In gdb can you go up to frame #7 and Also if you Thanks! |
thank you: this is the output (i'll try to take a look at older versions, if it worked before, maybe something changed on my env)
|
That makes no sense whatsoever!!! The kernel seems to be saying that the file that is being executed, and ld.so as well, are both ... the root directory. Wild guess: maybe there is some kind of security module or something present that is deliberately hiding the results in /proc/.../maps. That would cause this issue in rr. |
yes, this seems strange ! funny |
it seems that this |
running
rr
recordingls
I used it succesfully in docker before, so i wonder what can lead to that error so i can debug
The text was updated successfully, but these errors were encountered: