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
In Load mode, a hotkey of some sort enables a log in a seperate pane.
This log contains one or both of the following (i am not sure yet):
For each Breakpoint that has been hit, an entry in the form of BP in line 9 hit
For each value change in memory, an entry in the form of [h1]: 436 -> 437
For the second point, there might be the option to not include changes on all memory cells/accumulators/..., but only on some (that can be selected in some way). This selection would have to include a way to select index memory cells that are not yet contained in the memory cell listing on the right side.
The text was updated successfully, but these errors were encountered:
I like this idea, implementing it should not be too complicated (that is if we don't make memory values selectable and instead output everything that changes to the pane). I don't think that outputting everything in the log will be a bad idea, as there is at max one value that is changed per instruction (however this looks different, when run to breakpoints is used, but I think that is for now something we would have to life with).
In
Load
mode, a hotkey of some sort enables a log in a seperate pane.This log contains one or both of the following (i am not sure yet):
BP in line 9 hit
[h1]: 436 -> 437
For the second point, there might be the option to not include changes on all memory cells/accumulators/..., but only on some (that can be selected in some way). This selection would have to include a way to select index memory cells that are not yet contained in the memory cell listing on the right side.
The text was updated successfully, but these errors were encountered: