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
Although complex, a remote call API could be possible if done like this:
enum {
LM_REG_RAX=0,
...
LM_REG_MAX
};
enum {
LM_FPREG_XMM0=0,
...
LM_FPREG_MAX
}
structlm_callstate_t {
lm_byte_tstack[0xFF];
lm_uintptr_tregs[32]; // arch-dependent, accessed by LM_REG_*doublefpregs[16]; // arch-dependent, may not be available on some archs, accessed by LM_FPREG_*
}
lm_bool_tLM_RemoteCall(lm_process_t*process, lm_callstate_t*setup, lm_callstate_t*post_call);
It will setup the call using the call state, and then write the post-call state into an optional variable
On Linux/FreeBSD, this is """easily""" achievable with ptrace; on Windows, not sure.
The text was updated successfully, but these errors were encountered:
Although complex, a remote call API could be possible if done like this:
It will setup the call using the call state, and then write the post-call state into an optional variable
On Linux/FreeBSD, this is """easily""" achievable with ptrace; on Windows, not sure.
The text was updated successfully, but these errors were encountered: