diff options
| author | aldelaro5 <aldelaro5@gmail.com> | 2016-10-06 10:46:09 -0400 |
|---|---|---|
| committer | aldelaro5 <aldelaro5@gmail.com> | 2016-10-06 10:51:43 -0400 |
| commit | 549060c5b4c1e28a871930680d4ecc75d75520c5 (patch) | |
| tree | bc912764325ae3661a92ae12b30bddf0feaeb401 /Source/Core/DolphinWX/Debugger/MemoryWindow.cpp | |
| parent | 7b29b3c5711b5bdd41dd65f315f7bcb850637957 (diff) | |
Label debugger memchecks as "Memory Breakpoints" in the GUI
This is done to remove confusions among potential debugger users and to also make it more accurately tell what this feature is actually doing. Despite being true that it is using a memcheck (and it certianly checks that memory), the idea being to break on a memory access isn't really obvious especially considering that memchecks are also used in full MMU emulation to handle exceptions. It also doesn't help that memchecks are now supported in every builds.
It also changes the corresponding log because this log would be wanted by the user which means it should be more obvious that it was caused by the "memory breakpoint".
Diffstat (limited to 'Source/Core/DolphinWX/Debugger/MemoryWindow.cpp')
| -rw-r--r-- | Source/Core/DolphinWX/Debugger/MemoryWindow.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Source/Core/DolphinWX/Debugger/MemoryWindow.cpp b/Source/Core/DolphinWX/Debugger/MemoryWindow.cpp index a70ba2db94..f6b1fe259d 100644 --- a/Source/Core/DolphinWX/Debugger/MemoryWindow.cpp +++ b/Source/Core/DolphinWX/Debugger/MemoryWindow.cpp @@ -117,7 +117,7 @@ CMemoryWindow::CMemoryWindow(wxWindow* parent, wxWindowID id, const wxPoint& pos wxDefaultSize, data_type_options, 1); wxStaticBoxSizer* const memcheck_options_sizer = - new wxStaticBoxSizer(wxVERTICAL, this, "Memory check options"); + new wxStaticBoxSizer(wxVERTICAL, this, "Memory breakpoint options"); memcheck_options_sizer->Add(rdbReadWrite = new wxRadioButton(this, IDM_MEMCHECK_OPTIONS_CHANGE, "Read and Write", wxDefaultPosition, wxDefaultSize, wxRB_GROUP)); |