[hatari-devel] Moonspeeder problem : joystick question

Eero Tamminen eerot at users.berlios.de
Sun Jan 31 22:51:25 CET 2010


Hi,

On Sunday 31 January 2010, Eero Tamminen wrote:
> There are quite many different values it writes there:
>       $007f
>       $00bf
...

I added IMHO nice new feature to conditional breakconds to find out these
kind of issues.  Now, to see when a value of a specific memory address
changes, just give exactly the same expression for that address value on
both sides of the condition comparison.  To just see the value changes
without breaking, add "trace" keyword to the end of the whole expression.

Like this:
-----------
> b ($ffff9202).w ! ($ffff9202).w trace
CPU condition breakpoint 1 with 1 condition(s) added.
-> Track condition(s), show value(s) when matched.
-> Trace, show hits, but don't break.
-----------

Tracing is also shown in the conditional breakpoints list:
-----------
> b
1 conditional CPU breakpoints:
  1: ( $ffff9202 ) . w ! ( $ffff9202 ) . w, traced
-----------

The tracked breakpoint can have also additional conditions to make sure that
it's not triggered too often.

And naturally you can monitor changes happening to multiple addresses at
the same time just by adding more breakpoint with this kind of conditions.


The trace output of the example breakpoint looks like this with Moonspeader:
-----------
1. breakpoint conditions matched 1664 times.
  $ffff9202 = $df
1. breakpoint conditions matched 1665 times.
  $ffff9202 = $ffff
1. breakpoint conditions matched 1666 times.
  $ffff9202 = $fb
1. breakpoint conditions matched 1667 times.
  $ffff9202 = $ffff
1. breakpoint conditions matched 1668 times.
  $ffff9202 = $bf
-----------

I hope you'll like it. :-)


	- Eero



More information about the hatari-devel mailing list