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
Currently, Binary Ninja's TTD implementation allows recording and analyzing individual program executions. It would be valuable to add functionality to compare different TTD traces of the same program.
Use Case Example
Record TTD trace of program.exe with parameter A (trace1)
Record TTD trace of program.exe with parameter B (trace2)
Need ability to analyze and compare how these executions differ
Proposed Functionality
Load multiple TTD traces simultaneously
Compare execution paths between traces
Identify points where executions diverge
Compare memory states and register values at equivalent points
Visualize differences between traces
Benefits
Better understand how different inputs affect program flow
More efficient analysis of program behavior variations
Easier identification of key decision points in code
Enhanced reverse engineering capabilities
Current Limitation
Currently can only analyze one TTD trace at a time, making it difficult to understand how different program parameters or conditions affect execution paths.
Would this feature be feasible to implement in Binary Ninja's TTD implementation?
The text was updated successfully, but these errors were encountered:
Feature Request
Currently, Binary Ninja's TTD implementation allows recording and analyzing individual program executions. It would be valuable to add functionality to compare different TTD traces of the same program.
Use Case Example
Proposed Functionality
Benefits
Current Limitation
Currently can only analyze one TTD trace at a time, making it difficult to understand how different program parameters or conditions affect execution paths.
Would this feature be feasible to implement in Binary Ninja's TTD implementation?
The text was updated successfully, but these errors were encountered: