WinUAE debugger workflow: reset, disable breakpoints etc

[hop]

Originally Posted by hop

1. Debugger "reset" or "restart" command

I think I've been here before, but I've remembered that a useful workflow is to reset using the system tray context menu, then resume (g) execution in the debugger.

[Rock'n Roll]

only an idea for a new breakpoint concept for the WinUAE Debugger:

All 'f' commands:

f                     Step forward until PC in RAM ("boot block finder").
f <address> [Nx]      Add/remove breakpoint.
fa <address> [<start>] [<end>]
                    Find effective address <address>.
fi                    Step forward until PC points to RTS, RTD or RTE.
fi <opcode> [<w2>] [<w3>] Step forward until PC points to <opcode>.
fp "<name>"/<addr>    Step forward until process <name> or <addr> is active.
fl                    List breakpoints.
fd                    Remove all breakpoints.
fs <lines to wait> | <vpos> <hpos> Wait n scanlines/position.
fc <CCKs to wait>     Wait n color clocks.
fo <num> <reg> <oper> <val> [<mask> <val2>] Conditional register breakpoint [Nx] [Hx].
reg=Dx,Ax,PC,USP,ISP,VBR,SR. oper:!=,==,<,>,>=,<=,-,!- (-=val to val2 range).
f <addr1> <addr2>     Step forward until <addr1> <= PC <= <addr2>.

and I never get an answer on my questions to this command:

b                     Step to previous state capture position.

I believe 'b' is obsolet and free

From this side I suggest a new breakpoint concept.

In my opinion it would be better to rename some commands:

f <address>	Add/remove breakpoint.	   --> b	; breakpoint
fl		List breakpoints.	   --> bl	; list breakpoint
fd		Remove all breakpoints.    --> bd	; delete breakpoint
fo		Conditional register breakpoint     --> br	; register breakpoint
fp		process			   --> bp	; process breakpoint

So for search and find use 'f':

f				--> f	; boot block finder
fa				--> fa	; find address
fi				--> fi	; find instruction
f <addr1> <addr2>		--> fx [<addr1>][<addr2>] --> find executed pc address

for the special 'forward' commands:
fs				--> fs	; Wait n scanlines/position.
fc				--> fc	; Wait n color clocks.

Then there are different other breakpoints:
- program breakpoint
- memory watchpoint
- copper breakpoint
- exception breakpoint

And GUI Debugger shows program breakpoints and memory watchpoints under: F7 - BRKPTS

For this it would be good to get a command for:
bla ; list all breakpoints
bda ; delete all breakpoints

Action Replay is:
B: SHOW CURRENT BREAKPOINTS - B ADDRESS
BS: SET BREAKPOINT - BS ADDRESS
BD: DELETE BREAKPOINT - BD ADDRESS
BDA: DELETE ALL BREAKPOINTS - BDA

;---------------------------------------------------------------------------
a minor bug:

f <addr1> <addr2> Step forward until <addr1> <= PC <= <addr2>.
This debugger command is something like a breakpoint, but it breaks only once.

it doesn't work for <addr1> == PC == <addr2>
>f 319a0 319a0 ; it doesn't stopp the program here

it works for <addr1> = PC < <addr2>

>f 319a0 319a2 ; works
Cycles: 4194303 Chip, 8388607 CPU. (V=210 H=0 -> V=98 H=187)
...
000319a0 33c0 00df f040 move.w d0,$00dff040
Next PC: 000319a6
>

Maybe the command can be changed to:
fx [<addr1>][<addr2>] ; where only addr1 is like a breakpoint only once
; and with addr2 in range --> <addr1> = PC < <addr2>