|Re: [hatari-devel] Data access breakpoints?|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Data access breakpoints?
- From: Miro Kropáček <miro.kropacek@xxxxxxxxx>
- Date: Sat, 8 Sep 2018 10:00:31 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Gd0n6ykOCcsAZGSiiGDayfNU2JpU5qVAScXbOaMfnOw=; b=rZWX1Td8G0JF5BWZ1/wShWcxP9g2Lc/7Buwuz9b2QBSoRQ1zuVguxLeVSSCOFdMhut PVUMGE1SM1uBKkfZ4t55y8J6j6Tx0tdtO6Pt76UTKX6YpRQeBS0csNYzKfzxvKzFNck9 xqHn9I5S1vLhjKyzaAVaq6lMqwFdfFr/m/VJCrOlGQjHQseY+8A8DzCyOO9pDRT3cFEy U5ZWn6XJsZlxaHtkmi4TjmcG+uQTjVj9+bQl3YSbiUjCinoyI+gwes9j6A2PACt+w5ed czvS//NIsderVgXuo9xzTIG0/OU54FMljADKWeowBfJiNm80al+Qi9n88xnNoJV44g5k npTg==
unfortunately it's not supported yet, as this requires to intercept all
read/write acceses and can have much more impact on emulatoin speed than
just checking PC value for example.
Trust me, it can't be slower than trace cpu_disasm ;-)
So, you can't detect read access, but you can detect write accesses if
the value is changed. For example :
b (0xff8260.b) ! (0xff8260.b)
will break each time resolution is changed in $ff8260.
Yes, I'm aware of this. However as I mentioned, if I'm interested where in code a certain operation happens (accessing Videl for instance), sometimes it writes the same value again and again so this wont work.
I was thinking about something like
b (0xff8260.b) ! (0xff8260.b) || (0xff8260.b) = (0xff8260.b)
but I guess that would trigger every single cycle, not only when written.