Re: [hatari-devel] WinUAE core freeze with ST emulation

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

On maanantai 16 tammikuu 2012, Laurent Sallafranque wrote:
> But when the code returns to the running CPU (like m68k_run_1 (void),
> m68k_run_2 (void), ...) the value of SPCFLAG_BRK is back to 0 and the
> program doesn't return to m68k_go (that's where the change of CPU
> occurs).
> 
> I haven't managed to find this problem, and it's quite annoying. Some
> help would be appreciate on this one.

To find out when some variable changes, set a watchpoint in Gdb for it.
It's not only Hatari debugger that has them. :-)

$ gdb src/hatari
....
(gdb) watch nVBLs > 200
Watchpoint 1: nVBLs > 200
(gdb) info watchpoints 
Num     Type           Disp Enb Address    What
1       watchpoint     keep y              nVBLs > 200
(gdb) run --machine falcon --tos /home/emulation/atari/tos/etos512k.img 
....
Hardware watchpoint 1: nVBLs > 200

Old value = 0
New value = 1
Video_InterruptHandler_VBL () at /home/eero/work/hatari/src/video.c:2844
2844            Video_ClearOnVBL();
(gdb) del 1
(gdb) info watchpoints 
No breakpoints or watchpoints.


	- Eero