Skip to content
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

Injector: syscall.Ptrace*: no such process #13

Closed
jm33-m0 opened this issue Jan 14, 2021 · 2 comments
Closed

Injector: syscall.Ptrace*: no such process #13

jm33-m0 opened this issue Jan 14, 2021 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@jm33-m0
Copy link
Owner

jm33-m0 commented Jan 14, 2021

This seems to be an issue with golang itself.
When the tracee is not our child process, and/or ptrace attribute is not set to true, we lose control to the tracee immediately.

The reason: PtraceAttach and PtraceGetRegs are from different processes/threads

image

@jm33-m0 jm33-m0 added the bug Something isn't working label Jan 14, 2021
@jm33-m0 jm33-m0 changed the title syscall.Ptrace*: no such process Injector: syscall.Ptrace*: no such process Jan 14, 2021
@jm33-m0 jm33-m0 self-assigned this Jan 14, 2021
@jm33-m0
Copy link
Owner Author

jm33-m0 commented Jan 14, 2021

golang/go#7699

@jm33-m0
Copy link
Owner Author

jm33-m0 commented Jan 14, 2021

golang/go#43685
fixed with 464e151

@jm33-m0 jm33-m0 closed this as completed Jan 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant