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
When the target stops at an address and there is no function for it, the debugger will create a function at the address to allow the display of disassembly/ILs. This works well in most cases, however, when it comes to TTD backward debugging, stepping backwards in the code will create various function that only has one instructions in it, which severely limits the readability.
While a better approach for this would be to backward scan the execution trace to find the call/jmp instruction that leads to the function, but for now we might need a workaround for it.
The text was updated successfully, but these errors were encountered:
When the target stops at an address and there is no function for it, the debugger will create a function at the address to allow the display of disassembly/ILs. This works well in most cases, however, when it comes to TTD backward debugging, stepping backwards in the code will create various function that only has one instructions in it, which severely limits the readability.
While a better approach for this would be to backward scan the execution trace to find the call/jmp instruction that leads to the function, but for now we might need a workaround for it.
The text was updated successfully, but these errors were encountered: