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.

Sign up for GitHub

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

Jump to bottom

PTRACE_POKETEXT instead of syscall from libc? #4

Open
Mic92 opened this issue Jan 12, 2021 · 0 comments
Open

PTRACE_POKETEXT instead of syscall from libc? #4

Mic92 opened this issue Jan 12, 2021 · 0 comments

Comments

@Mic92
Copy link

Mic92 commented Jan 12, 2021

I want to adapt your code to a static linked executable.
I see why you want to use libc for your project (portability).
However I was wondering if there is any major issue you see with just using
PTRACE_POKETEXT to write the syscall instruction to the current instruction?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Mic92