Re: [hatari-devel] Debbuger - MMU Status register

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi Thomas,

Thanks, I added note about it to release notes.


Regarding "TODO: Also call mmu_dump_tables() here"... If it dumps a lot 
of data (e.g. mappings  for all m68k-Linux user-space processes), it's 
probably better as a separate "info" command option (e.g. "mmu-tables".


	- Eero

On 3.4.2022 14.06, Thomas Huth wrote:
> Am Mon, 17 Jan 2022 22:02:47 +0100
> schrieb Cyprian Konador <cyprian.konador@xxxxxxxxx>:
>
> > On Sun, 16 Jan 2022 at 08:58, Thomas Huth  wrote:
> >
> > > Am Thu, 6 Jan 2022 22:08:29 +0100
> > > schrieb Cyprian Konador:
> > >   
> > > > Hi Team,
> > > >
> > > > "r" command doesn't (or I can't see it) show the MMUSR register.
> > > > Below you can find my console output.
> > > > Is it ok? Or maybe should I enter another command?
> > >
> > > Looks like this hasn't been wired up yet. There's a mmu_dump_tables()
> > > in the WinUAE CPU core code, but the Hatari debugger does not seem to
> > > call that yet... and it's likely only for 68040 and 68060 mode anyway.
> > > I guess we have to write such a function for 68030 on our own in Hatari?
> > >   
> >
> > I had a plan to add that on my own. Unfortunately, I have no working
> > environment for compiling Hatari at that moment.
>
> FWIW, I've added an "info mmu" command now:
>
>   https://git.tuxfamily.org/hatari/hatari.git/commit/?id=14013d4696b
>
> I hope that's basically what you needed.
>
>   Thomas