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
This would allow easy visualization of the frame rendering timeline in GPUView.
It will help modify the hook_d3d to optimize performance and reduce latency.
I would propose to emit one event each time a hook callback function is called, so it should be implemented in hook_main.
Before putting a big effort on it, do you think it makes sense @JeremyAnsel ?
An additional feature could be generating a ETW on demand for a list of given call instructions, provided by their address in a config file.
This would allow a low-overhead dynamic instrumentation of xwingalliance.exe useful for reversing and hooking analysis/design.
Hook_main would need to implement the necessary memory patching to capture the flow without altering the execution.
Is this second feature even feasible?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
This would allow easy visualization of the frame rendering timeline in GPUView.
It will help modify the hook_d3d to optimize performance and reduce latency.
I would propose to emit one event each time a hook callback function is called, so it should be implemented in hook_main.
Before putting a big effort on it, do you think it makes sense @JeremyAnsel ?
An additional feature could be generating a ETW on demand for a list of given
call
instructions, provided by their address in a config file.This would allow a low-overhead dynamic instrumentation of xwingalliance.exe useful for reversing and hooking analysis/design.
Hook_main would need to implement the necessary memory patching to capture the flow without altering the execution.
Is this second feature even feasible?
Thanks in advance!
The text was updated successfully, but these errors were encountered: