simulator reset

[Onkar Shinde]

while debugging and running the simulator repeatedly, it is getting clear that most runtime values simply stick around between each run. However, when watching the simulator work, it would be better to have a way to reset it to some pre-defined state - i.e. via a toolbar button that allows the user to reset the simulator.
Preferably, this would also allow for certain components to be excluded, so that the user may pick "reset" and then a number of options with checkboxes that shows "stack,memory, registers".

[Bug Importer (bug-importer)]

this is available via the menu!

[Bug Importer (bug-importer)]

reset doesn't however reset the stack trace

[Bug Importer (bug-importer)]

this might also benefit from being exposed via the toolbar?

[Onkar Shinde (onkarshinde)]

There is already a reset button. I will see if I can add functionality of resetting stack.
The button is already available on toolbar.

[Onkar Shinde (onkarshinde)]

Sridhar,

Can you please comment on this issue? Do you think it is important to have functionality to reset stack. If you think it is important then please review attached patch.

[Sridhar Ratnakumar (srid)]

AFAIK, stack itself is stored in the memory ... and grows downward. The address of stack pointer is stored in the 'SP' register. Try this:

1. Load nqueeus.asm and execute it till first break point
2. Note the stack; and also directly inspect memory addresses of stack
3. Stop the program; note that the stack memory (on left panel 'Memory') is still intact
4. Reset -> Memory
5. Memory is now reset, including the addresses of stack

Therefore we shouldn't need a separate reset for stack.

The 'Stack' tab on the right panel is meant to be useful only when the program is actually running or being debugged. When the program is stopped, it shows the previous stack snapshot (address in last value of 'SP'). I noticed that when 'Reset' is clicked, this stack tab (including the 'Data' tab) is not redrawn ... which is a bug.

[The Escapist (wisd00m)]

I think that's a good analysis: the issue is not about resetting the actual stack, but rather about resetting/redrawing the the "data tab".