Here is a patch for the firs suggestion. I have added the save code in the debugger manager, because there is a member variable who is related to the mode. I also added the DebuggerManager::Free() call in the Manager::Shutdown() function. See the forum post http://forums.codeblocks.org/index.php/topic,21923.msg149105/topicseen.html#msg149105
There was also a no range check bug in DisassemblyDlg::SetActiveAddress(uint64_t addr)
Ok , i created three patches:
FIX_503_memory_bug : Fixes a overflow error and calls the DebuggerManager Free function. This are not related to this ticket but i found them while implementing it, so i post them here
FIX_503_examine_memory_02: Save the setting from the examine memory dialog. This time don't use the destructor as obfuscated pointed out in the forum thread
FIX_503_disassembly_dlg_02 : Save the setting from the disassembly dialog, again not in the destructor but in the ui event handler
Steps to reproduce on windows 7:
1) open a project
2) Add some breakpoint
3) Start debugger
4) open the disassembly window
5) stop the debugger
6) start the debugger (now with the disassembly window open on startup of the debugger)
7) crash
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
also it would be nice to to save selected dump size on memory dump window.
Here is a patch for the firs suggestion. I have added the save code in the debugger manager, because there is a member variable who is related to the mode. I also added the DebuggerManager::Free() call in the Manager::Shutdown() function. See the forum post http://forums.codeblocks.org/index.php/topic,21923.msg149105/topicseen.html#msg149105
There was also a no range check bug in DisassemblyDlg::SetActiveAddress(uint64_t addr)
Last edit: bluehazzard 2017-04-30
here is part two, for the examine memory dlg
Ok , i created three patches:
FIX_503_memory_bug : Fixes a overflow error and calls the DebuggerManager Free function. This are not related to this ticket but i found them while implementing it, so i post them here
FIX_503_examine_memory_02: Save the setting from the examine memory dialog. This time don't use the destructor as obfuscated pointed out in the forum thread
FIX_503_disassembly_dlg_02 : Save the setting from the disassembly dialog, again not in the destructor but in the ui event handler
patch 2 and 3
I've pushed almost everything, except the out-of-bounds fix.
Can you tell me how to reproduce the problem? I'm not really sure this is the correct fix.
Steps to reproduce on windows 7:
1) open a project
2) Add some breakpoint
3) Start debugger
4) open the disassembly window
5) stop the debugger
6) start the debugger (now with the disassembly window open on startup of the debugger)
7) crash
Everything should be applied in trunk/master now.