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
Current behavior
When setting registers at an address 0x08049196 in the register manager, the emulator will apply those registers when I Emulate program in new trace at that address. All general purpose registers will be applied except for the stack pointer.
By default the stack pointer will be set to some arbitrary value. In this example, it's set to 0x5000 but my register manager has the stack pointer set to 0xffffd2bc. The address 0xffffd2bc is inside a valid and initialized block in my Memory map.
Desired behavior
When starting the emulator at an address that has the stack pointer set in the register manager, I'd like the emulator to use that stack pointer by default, rather than having to manually editing the stack pointer after I start the new trace
The text was updated successfully, but these errors were encountered:
FWIW, an alternative is to create an uninitialized block called "STACK" in the Memory Map. The SP should get initialized to the highest address (maybe +1) in that block. Granted, that winds up applying to the entire program rather than just the specific function.
Current behavior
When setting registers at an address
0x08049196
in the register manager, the emulator will apply those registers when IEmulate program in new trace
at that address. All general purpose registers will be applied except for the stack pointer.By default the stack pointer will be set to some arbitrary value. In this example, it's set to
0x5000
but my register manager has the stack pointer set to0xffffd2bc
. The address0xffffd2bc
is inside a valid and initialized block in my Memory map.Desired behavior
When starting the emulator at an address that has the stack pointer set in the register manager, I'd like the emulator to use that stack pointer by default, rather than having to manually editing the stack pointer after I start the new trace
The text was updated successfully, but these errors were encountered: