You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
Now that the processes store their architecture in
lm_process_t
, perhaps the use ofprocess->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 takebits
as parametersThe text was updated successfully, but these errors were encountered: