Re: [hatari-devel] MEMWATCH freezes Hatari |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] MEMWATCH freezes Hatari
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Tue, 23 Oct 2018 18:37:00 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1540312620; s=strato-dkim-0002; d=seimet.de; h=In-Reply-To:References:Message-ID:Subject:To:From:Date: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=tjCnOwjloSRlZtecYHOG0xd4120DhcvwOWgmwUBfMzU=; b=ZtoKaynqzM31/5AZc4iPBE/xsntqbMK+zm754uaOEGkr9GksahHBg6Cc1O9ELpQHy7 nIcYPMv+ffebcL3RHwenFlcbkjWTpPwQHPQvVHNb94F1gOJPvbXzETG6hzMhqx5p8rHe BICMnOOXOFgWe1m3leA51vsQpE+4KagBbfF6kXRUkhJ2IxGPFpQT8SYaBfcaL5YCHXQy QQGtioCrONwt4yRcOTfCHfbG8Lr3Jkm6COyuXURlGbWnxSKLfOaTrnm5qvNOQwcG1xWz 7nxniJwEhpfndKgdjmPpTmOmScNqmwTiSq3eC/whh/6WRLPzmttbQHMw/7mrD51LRn5r c+Jw==
Today (note that I did not recompile anything ...) the situation is a
bit different. PD does not crash anymore, but Tempus Word still does.
This time, when PMMU and PF and CE are enabled, Tempus Word crashes with
a double bus fault. When only PMMU is enabled it freezes, then there are
14 bombs, and after some time (about 5 seconds) Hatari crashes with a
segfault.
Even though I compiled with -g gdb only shows this:
Thread 1 "hatari" received signal SIGSEGV, Segmentation fault.
0x00005555578a4f3c in regs ()
(gdb) bt
#0 0x00005555578a4f3c in regs ()
#1 0x0000000000000000 in ?? ()
So all in all, the symptoms of the problem are still the same: Either
freezing or a double bus fault.
> > Note that when I am testing I start Hatari without PMMU, CE and PF
> > enabled. I enable them by pressing F12 and reconfiguring, and then
> > resetting Hatari. Maybe this has some relevance.
>
> Does it happen if only more compatible/prefetch (I don't know how it is
> called in Hatari) and data cache is enabled? (No cycle-exact)
>
> There is still something wrong with data cache emulation (at least when
> also MMU is enabled, this is also not a new bug) but it is really
> difficult to debug because actual problem may have happened thousands of
> instructions ago before it causes any visible side-effects..
>
> I can only duplicate it with Amix that outputs "illegal instruction"
> during boot but there is no illegal instruction exceptions being
> generated so I am not really sure what it means. Unfortunately it also
> continues booting (instead of hanging/halting). No data cache emulation,
> no above error.
>
>