Re: [hatari-devel] memory setup segfault

[ Thread Index | Date Index | More lists.tuxfamily.org/hatari-devel Archives ]


Hello,


I wish this helps :

I've just started Hatari with --log-level debug, waiting to reach the Desktop, and switch to ST.


laurent@laurent-Gamer:~/Atari/hatari/build/src$ ./hatari --log-level debug
DEBUG: Video_SetSystemTimings 5 3 -> 2 (WS3) 503 503 64
INFO : Hatari v2.5.0-devel (Nov  5 2023), compiled on:  Nov  5 2023, 18:47:44
DEBUG: Video_SetSystemTimings 5 3 -> 2 (WS3) 503 503 64
DEBUG: Configured max Hatari resolution = 832x588, optimal for ST = 832x552(+36)
DEBUG: update cyc speed 0 throttle 0.000000 clock_mult 512
DEBUG: CPU cycleunit: 256 (0.500)
DEBUG: 1872 CPU functions
DEBUG: ACSI: 0, SCSI: 0, IDE: 0 - GEMDOS skipping 0 partitions.
DEBUG: Checking GEMDOS C: HDD: /media/Toshiba/Data_Laurent/Jeux/Atari/DiskDur.FAL INFO : GEMDOS HDD emulation, C: <-> /media/Toshiba/Data_Laurent/Jeux/Atari/DiskDur.FAL. DEBUG: memory_map_Standard_RAM total=14680064 ram0=0 ram1=0 mmu0=131072 mmu1=131072
DEBUG: Loaded TOS version 4.04, starting at $e00000, country code = 127, PAL
DEBUG: Skipped patch 'disable PMMU access'.
2 repeats of: DEBUG: Skipped patch 'disable PMMU access'.
DEBUG: Applying TOS patch 'ROM checksum'.
DEBUG: Applying TOS patch 'boot from DMA bus'.
DEBUG: Applying TOS patch 'boot from DMA bus'.
DEBUG: Skipped patch 'replace code for 68040'.
8 repeats of: DEBUG: Skipped patch 'replace code for 68040'.
16 repeats of: DEBUG: Skipped patch 'replace code for 68040'.
2 repeats of: DEBUG: Skipped patch 'replace code for 68040'.
DEBUG: Skipped patch 'replace code for 68060'.
8 repeats of: DEBUG: Skipped patch 'replace code for 68060'.
16 repeats of: DEBUG: Skipped patch 'replace code for 68060'.
6 repeats of: DEBUG: Skipped patch 'replace code for 68060'.
DEBUG: Applying TOS patch 'enable extra TT RAM on Falcon'.
DEBUG: Applying TOS patch 'enable extra TT RAM on Falcon'.
DEBUG: Applied 5 TOS patches, 0 patches failed.
DEBUG: Video_SetSystemTimings 5 3 -> 2 (WS3) 503 503 64
DEBUG: Video_SetSystemTimings 5 3 -> 2 (WS3) 503 503 64
DEBUG: SCSI BUS reset
DEBUG: Microphone_Start: freq = 50066
DEBUG: Host system has accurate delays. (1)
DEBUG: update cyc speed 0 throttle 0.000000 clock_mult 512
DEBUG: CPU cycleunit: 256 (0.500)
DEBUG: Building CPU, 45926 opcodes (3 -2 1)
DEBUG: CPU=68030, FPU=68882 (host 64b), MMU=68030, JIT=0.
DEBUG:  ~cycle-exact
DEBUG:  no unimplemented floating point instructions
DEBUG:  24-bit
DEBUG:
DEBUG: update cyc speed 0 throttle 0.000000 clock_mult 512
DEBUG: CPU cycleunit: 256 (0.500)
DEBUG: hardreset, memory cleared
DEBUG: m68k_run_mmu030
DEBUG: CPU reset PC=e00038 (ROM memory)..
DEBUG: memory_map_Standard_RAM total=14680064 ram0=0 ram1=0 mmu0=0 mmu1=0
DEBUG: SDL2 window event: 0x1
DEBUG: SDL2 window event: 0x2
DEBUG: SDL2 window event: 0x1
DEBUG: SDL2 window event: 0x4
DEBUG: SDL2 window event: 0xa
DEBUG: SDL2 window event: 0xc
DEBUG: SDL2 window event: 0xf
DEBUG: SDL2 window event: 0x6
DEBUG: SDL2 window event: 0x5
DEBUG: SDL2 window event: 0x3
DEBUG: 68030 MMU enabled. Page size = 32768 PC=00e014f6
DEBUG: Calling DSP_Reset?
DEBUG: SDL2 window event: 0x6
DEBUG: SDL2 window event: 0x3
DEBUG: SCSI BUS reset
DEBUG: SDL2 window event: 0xb
DEBUG: SDL2 window event: 0xd
DEBUG: raw_scsi: selected scsi id mask (01)
DEBUG: raw_scsi: selected non-existing id 0
2 repeats of: DEBUG: raw_scsi: selected non-existing id 0
DEBUG: raw_scsi: selected scsi id mask (02)
DEBUG: raw_scsi: selected non-existing id 1
2 repeats of: DEBUG: raw_scsi: selected non-existing id 1
DEBUG: raw_scsi: selected scsi id mask (04)
DEBUG: raw_scsi: selected non-existing id 2
2 repeats of: DEBUG: raw_scsi: selected non-existing id 2
DEBUG: raw_scsi: selected scsi id mask (08)
DEBUG: raw_scsi: selected non-existing id 3
2 repeats of: DEBUG: raw_scsi: selected non-existing id 3
DEBUG: raw_scsi: selected scsi id mask (10)
DEBUG: raw_scsi: selected non-existing id 4
2 repeats of: DEBUG: raw_scsi: selected non-existing id 4
DEBUG: raw_scsi: selected scsi id mask (20)
DEBUG: raw_scsi: selected non-existing id 5
2 repeats of: DEBUG: raw_scsi: selected non-existing id 5
DEBUG: SDL2 window event: 0xa
DEBUG: SDL2 window event: 0xb
DEBUG: SDL2 window event: 0xa
DEBUG: SDL2 window event: 0xb
DEBUG: SDL2 window event: 0xa
DEBUG: SDL2 window event: 0xc
DEBUG: SDL2 window event: 0xf
DEBUG: STMemory_RAM_SetBankSize total=1024 KB bank0=512 KB bank1=512 KB MMU=5
DEBUG: Video_SetSystemTimings 0 3 -> 2 (WS3) 503 503 64
DEBUG: memory_map_Standard_RAM total=1048576 ram0=524288 ram1=524288 mmu0=0 mmu1=0
DEBUG: memory_map_Standard_RAM - enable MMU 1048576 0 0
Erreur de segmentation (core dumped)
laurent@laurent-Gamer:~/Atari/hatari/build/src$


Le 05/11/2023 à 22:36, Nicolas Pomarède a écrit :
Le 05/11/2023 à 17:08, Laurent Sallafranque a écrit :
Another tests, I've switched from Falcon to TT (OK)

Then, I've switched from TT to ST and I get the core dump.


I've also configured hatari in TT mode, then I've saved the config, quit hatari and run it to start in TT mode.

When I swith to ST mode, I get the core dump.


Hi

I can't get the crash.

can you add option "--log-level debug" to your command line when running hatari and see what you get for DEBUG lines with "memory" (for example "DEBUG: memory_map_Standard_RAM") and post the results ?

Nicolas



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/