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

Reconsider uses of process->bits #226

Open
rdbo opened this issue May 29, 2024 · 1 comment
Open

Reconsider uses of process->bits #226

rdbo opened this issue May 29, 2024 · 1 comment

Comments

@rdbo
Copy link
Owner

rdbo commented May 29, 2024

Now that the processes store their architecture in lm_process_t, perhaps the use of process->bits is no longer required (or should be minimized)
Another thing that should be analyzed is functions like generate_hook_payload and ptrace functions that take bits as parameters

@rdbo
Copy link
Owner Author

rdbo commented May 29, 2024

Another thing to consider before going deep on this: architectures are still compiled separately. So if bits is not enough to distinguish one architecture from another (e.g x86 from x64), maybe it's time to create a port for that specific architecture, while still using bits for the architectures that allow for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant