Pizzapower's OpenMSX debugger improvements | MSX Resource Center (Page 2/3)

Master (172)

21-04-2023, 02:52

Here is a killer feature I wanted to do for a long time: Added preferences option to preserve breakpoint connected to symbol name when symbol file changes. This means that if you are debugging your code, you can reload the symbol file if it changed (if your code was recompiled for instance) and the breakpoints that point to symbols will me updated if their addresses have changed.

By max_iwamoto

Paladin (673)

21-04-2023, 03:11

pizzapower wrote:

Here is a killer feature I wanted to do for a long time: Added preferences option to preserve breakpoint connected to symbol name when symbol file changes. This means that if you are debugging your code, you can reload the symbol file if it changed (if your code was recompiled for instance) and the breakpoints that point to symbols will me updated if their addresses have changed.

That's would be great. It will save a lot of time.

Another feature I can think of is ability search RAM/VRAM/ROM for text/data.

By pizzapower

Master (172)

21-04-2023, 04:08

max_iwamoto wrote:

pizzapower wrote:

Here is a killer feature I wanted to do for a long time: Added preferences option to preserve breakpoint connected to symbol name when symbol file changes. This means that if you are debugging your code, you can reload the symbol file if it changed (if your code was recompiled for instance) and the breakpoints that point to symbols will me updated if their addresses have changed.

That's would be great. It will save a lot of time.

Another feature I can think of is ability search RAM/VRAM/ROM for text/data.

I think there is a TCL script that already does that. At least for RAM.

By DarkSchneider

Paragon (1030)

21-04-2023, 12:22

pizzapower wrote:

Here is a killer feature I wanted to do for a long time: Added preferences option to preserve breakpoint connected to symbol name when symbol file changes. This means that if you are debugging your code, you can reload the symbol file if it changed (if your code was recompiled for instance) and the breakpoints that point to symbols will me updated if their addresses have changed.

A nice and needed feature.

Another nice one would be involving watch the main RAM. When we use the memory mapper, we have the option to use "add debuggable viewer", then set it as "Main RAM". That option is good if you want to view the RAM in a lineal way. But if you want to watch a segment have to multiply page size 0x4000 by the segment you want to see, then search manually scrolling to the address.
Then it would be nice to have another option like "RAM segment" allowing to choose the segment number to watch its 16KB of data.

By pizzapower

Master (172)

22-04-2023, 17:29

DarkSchneider wrote:

A nice and needed feature.

Another nice one would be involving watch the main RAM. When we use the memory mapper, we have the option to use "add debuggable viewer", then set it as "Main RAM". That option is good if you want to view the RAM in a lineal way. But if you want to watch a segment have to multiply page size 0x4000 by the segment you want to see, then search manually scrolling to the address.
Then it would be nice to have another option like "RAM segment" allowing to choose the segment number to watch its 16KB of data.

Not sure, but I think this requires the creation of a new debuggable on OpenMSX side that maps to memory mapper, since that on the debugger side the widget seems like a generic memory dump of a debuggable.

By pizzapower

Master (172)

04-06-2023, 20:04

The debugger now has a menu item to capture code from the Code View to the clipboard:

Only the currently visible window is copied, but I plan to create a dialog that specifies the memory region.