Open karliss opened 5 years ago
In r2, when you enable "emu.str" it will enable "asm.emu" because, iirc, "emu.str" can't work when "asm.emu" is disabled.
Should this be handled from r2?
# both variables are set to false
[0x00005ae0]> e asm.emu
false
[0x00005ae0]> e emu.str
false
# enable emu.str
[0x00005ae0]> e emu.str=true
[0x00005ae0]> e emu.str
true
# show that asm.emu became true
[0x00005ae0]> e asm.emu
true
# set emu.str to false again
[0x00005ae0]> e emu.str=false
[0x00005ae0]> e emu.str
false
# this does not affect asm.emu that previously became true and still is
[0x00005ae0]> e asm.emu
true
Expected behavior in issue description is only one of the options. I am fine with preserving r2 behavior if Cutter GUI matches it. Third option is disabling emu.str option in cutter when asm.emu isn't enabled.
Environment information
Describe the bug
Disabling emu.str keeps asm.emu enabled.
To Reproduce Test 1
Test 2
Expected behavior
After disabling "emu.str" output returns to previous state.