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 would be very helpful if you can add support for additional, more basic, tracing formats.
In many cases a collection of execution addresses is available but not the registers / memory.
If would be awesome if you could add support for a module + offset format like lighthouse (or additional formats as described here).
The text was updated successfully, but these errors were encountered:
Since Tenet traces are 'lossy' as is, you can just output an trace containing eip=... or rip=... and it should just work without any putting any other registers/mem in the trace. Try it!
I can certainly add 'mod+off' support, and it makes sense when dealing with something as simple as an instruction trace. I have to be at least a little bit more careful with how I translate or represent 'mod+off' in the views for a more standard trace though. I think that's probably one of the main reasons I didn't try to get it into the initial release.
First of all, awesome project!
It would be very helpful if you can add support for additional, more basic, tracing formats.
In many cases a collection of execution addresses is available but not the registers / memory.
If would be awesome if you could add support for a
module + offset
format like lighthouse (or additional formats as described here).The text was updated successfully, but these errors were encountered: