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
It is also possible to record the content of CPU registers but this would slow
down acquisition and increase the size of traces significantly
Does this mean TracerGrind / TracerPIN can do it already? Or does it mean, in principle, a DBI framework can do this?
If the first is the case: How can I tell the tracer to include the register values in the trace?
If the second is the case: Do you have any hints for me how to extend TracerGrind / TracerPIN to support the tracing of register values?
Thanks for your help!
Best regards
The text was updated successfully, but these errors were encountered:
What format would you suggest for a (hypothetical) trace including register values? E.g. the name of the register in ASCII text followed by the value in 'raw' bytes?
Hi!
In your paper you write:
Does this mean TracerGrind / TracerPIN can do it already? Or does it mean, in principle, a DBI framework can do this?
If the first is the case: How can I tell the tracer to include the register values in the trace?
If the second is the case: Do you have any hints for me how to extend TracerGrind / TracerPIN to support the tracing of register values?
Thanks for your help!
Best regards
The text was updated successfully, but these errors were encountered: