![]() |
![]() |
#21 |
Registered User
Join Date: Apr 2019
Location: UK
Posts: 277
|
|
![]() |
![]() |
#22 |
German Translator
Join Date: Aug 2018
Location: Drübeck / Germany
Age: 50
Posts: 214
|
only an idea for a new breakpoint concept for the WinUAE Debugger:
All 'f' commands: Code:
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>. Code:
b Step to previous state capture position. From this side I suggest a new breakpoint concept. In my opinion it would be better to rename some commands: Code:
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 Code:
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> |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Easy PC -> Amiga IFF workflow? | arpz | Graphics | 12 | 06 September 2022 14:33 |
Debugger updates (was: WinUAE Debugger HH PC history) | selco | support.WinUAE | 8 | 14 March 2018 22:27 |
Disable Taskswitching in WinUAE-Debugger | selco | support.WinUAE | 2 | 22 February 2016 13:40 |
WinUAE Debugger - Audio Register Breakpoints | SparkyNZ | Coders. Asm / Hardware | 2 | 14 June 2015 21:40 |
WinUAE Debugger - Breakpoints when memory read | SparkyNZ | Coders. Asm / Hardware | 5 | 07 March 2015 23:48 |
|
|