| Re: [hatari-devel] Debugger memdump command + MMU address translation? |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: Nicolas Pomarède <npomarede@xxxxxxxxxxxx>, hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Debugger memdump command + MMU address translation?
- From: Markus Fröschle <markus@xxxxxxx>
- Date: Sat, 25 Feb 2023 16:42:26 +0100
- Ui-outboundreport: notjunk:1;M01:P0:z63QKTlXnSE=;QsOs0hQyCplgrD6T5vOjMjJbTOj B7o7vpQVEMTtCiSg6Xlm53ofNVzdhMrxTd8IA5aQVtJLkp+w+OZ4hqHUQutagW3XopyxxYTrH OPekatuNUiWWhp5Cd7Wy1Yy4g2NlOd5VvJTpGeGtcbqKHUk+XNsxW5uTt3jx2xsWPKNdORUuE 7Ou9G7xh82TkMqSpxSZtJvfXKSVv36SAfzv/u1SwvJo8IjX7BYB+dMg/1TnjczRnpHCzcnko0 5yr4CjCJjYfptn1MG6bkusSMBRweU9WIEbjA2jN0KuJGi///oCX12hq3tvXNF0qIF9Xv/Zesk fP4YdHfCIi6qUL8l+IEoN2LlucetMYKVIA03/YOkwhzE6yFnyUrhpLkwbfLMYV2A4OHtWjrBi aejag5ONqtc/Vd9VVrAKC4kYLSKI2PTYbpO/7yekN20XO1KlJBPM5MEuFHxSczuDx6xM/teaa 9UcP3mYrSLMoxjOf8f8xpbvSrZx2QYE2uuWXbb1RqiLbFKnoWMGZvu0bdA0Ykc4jAQYGctv5J 6vu2LQkiIH+cEZ6tTttYLJwVld5qo8GWwd1BDwnFdG+n2gZa/5XuhDU4+KOQ0nsj/ScrV+N7r 9zQ9+5VLzkZDJnXC6f2DOBuK22JHNsPIUFLuMTzNKpyLSuLAzHBRgFe/p0pjmgJ0a/Erh7nYi r+4IAmEfpUyzYzzZEATu+qETHashS3ZbIu451/OZAg==
Am Freitag, dem 24.02.2023 um 18:42 +0100 schrieb Nicolas Pomarède:
> Le 24/02/2023 à 16:55, Markus Fröschle a écrit :
> > ...
> > I only get a dump of zeros (what seems to be the error return value
> > from STMemory_Read()) although emulation in general (like bsrs and
> > rets) seem to work fine with stack read/write.
> >
> > Is this a bug or just a missing feature?
> >
> >
> ...
> I would need to check the code to be sure, but it's quite likely (you
> can check manually if it's broken/mising by reading the MMU tables
> and
> doing the translation yourself and see if this makes A7 points to a
> more
> "consistent" part of the memory).
Thanks.
As far as I can tell from the code, there appears to be no attempt to
do any MMU address translation in the memdump debugger function.