Issue: When manually adding a break point or updating an existing break point in the debugger, the values saved do not reflect what was entered into the form.
Steps to recreate:
1) Open a valid ROM file.
2) Once running, open the Debugger
3) In the Break points pane on the bottom of the debugger, right click and select Add or press Insert to add a new break point.
4) Select a Break Point Type (issue applies to all)
5) Select value(s) for Break On (issue applies to all)
6) Select a value for Address (issue applies to all)
7) Enter a valid address or address range
8) Click OK
The resulting break point will be always be saved as a CPU Memory type that breaks on Execution with the address FFFFFFFF.
Issue: When manually adding a break point or updating an existing break point in the debugger, the values saved do not reflect what was entered into the form.
Steps to recreate: 1) Open a valid ROM file. 2) Once running, open the Debugger 3) In the Break points pane on the bottom of the debugger, right click and select Add or press Insert to add a new break point. 4) Select a Break Point Type (issue applies to all) 5) Select value(s) for Break On (issue applies to all) 6) Select a value for Address (issue applies to all) 7) Enter a valid address or address range 8) Click OK
The resulting break point will be always be saved as a CPU Memory type that breaks on Execution with the address FFFFFFFF.
The resulting break point XML is: `
`
Mono:
Mono JIT compiler version 6.12.0.90 (tarball Fri Sep 4 14:02:38 UTC 2020) Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com TLS: __thread SIGSEGV: altstack Notifications: epoll Architecture: amd64 Disabled: none Misc: softdebug Interpreter: yes LLVM: yes(610) Suspend: hybrid GC: sgen (concurrent by default)Mesen: v 0.9.9