| 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: Mon, 22 Oct 2018 22:34:47 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1540240488; 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=JhyaiB4OFHgLsO+oiJH7tzEFUsfycKNGCSvBgbjuKEU=; b=tVRWwWK8GRzRN7/YsiYIDmB6P/mDRjlOE3GXNHEAfziDaFtgJSr1dW4pNsBHmTbksm 7uW4r6xl4Miv9MIP4SxB+6u1J+Ep1WnHDAKKhQ8oIQaYhEP3/hv+9wDcLdsq+Ad1X85F pjqvxUUdbu3GIpi78FMAbc9XdhX7h77UymM+CwVw/xj9dC9r1JJ245hV2ZzZSIUWJIv/ pQrKg0ePyCjv+ESQbqvDWbNNVw2v8GGLUzdbrAnHyqP2kurN+DCoXAEcD2dMQ4hBuaLU GC3Uv1jvWk3c5GxCj9Vdbw9d45m2R9deg+ckQhjLv8eWUWKUExCD8wHK49TT1QvJSryI MoqA==
With these changes and CE and PF I still get the segfault in the inlined
code:
#0 0x00005555578a4f00 in regs ()
#1 0x0000000000000003 in ?? ()
#2 0x0000555555ec641f in get_iword_mmu030c_state (o=4)
at /home/us/hatari/hatari/src/cpu/cpummu030.h:818
#3 op_41e8_35_ff (opcode=<optimized out>)
at /home/us/hatari/hatari/src/cpu/cpuemu_35.c:16676
#4 0x000055555593852b in m68k_run_mmu030 ()
at /home/us/hatari/hatari/src/cpu/newcpu.c:6623
#5 0x000055555593349a in m68k_go (may_quit=<optimized out>)
at /home/us/hatari/hatari/src/cpu/newcpu.c:7719
#6 0x00005555558701ab in main (argc=1, argv=<optimized out>)
at /home/us/hatari/hatari/src/main.c:949
Just before the segfault 11 bombs are displayed.
> Le 22/10/2018 à 22:00, Nicolas Pomarède a écrit :
> > Le 22/10/2018 à 21:03, Uwe Seimet a écrit :
> >> Hi,
> >>
> >> Yes, this is what also worked for me. I think I wrote ST-RAM once in my
> >> previous posting, meaning TT-RAM. Please try with 8 MB ST-RAM and 16 MB
> >> TT-RAM. This crashed for me with the segmentation fault I posted.
> >>
> >
> > I just tested with 8 MB ST, 16 MB TT, 68030+68882+MMU with CE mode TOS
> > 3.06FR, TT high res and no bus error or segfault.
> > the mystery is still there ...
>
> I just pushed some more fixes from WinUAE to handle LRMW accesses as
> well as unaligned memory accesses in case of bus error with retry.
> Not sure it changes anything for you, but who knows.
>
>
>