Description of problem: Crashed running Omikron basic: Hatari v1.6.2, compiled on: Jul 20 2012, 03:05:08 Building CPU table for configuration: 68000 (compatible mode) GEMDOS HDD emulation, C: <-> /home/roel/atari. Detected scancode offset = 8 (key: 'left shift' with scancode $32) hatari: /builddir/build/BUILD/hatari-1.6.2/src/cycInt.c:378: CycInt_AddRelativeInterruptWithOffset: Assertion `CycleTime >= 0' failed. Aborted (core dumped) Version-Release number of selected component: hatari-1.6.2-2.fc18 Additional info: backtrace_rating: 4 cmdline: hatari crash_function: CycInt_AddRelativeInterruptWithOffset executable: /usr/bin/hatari kernel: 3.7.4-204.fc18.x86_64 remote_result: NOTFOUND uid: 578 Truncated backtrace: Thread no. 1 (5 frames) #4 CycInt_AddRelativeInterruptWithOffset at /usr/src/debug/hatari-1.6.2/src/cycInt.c:378 #5 CycInt_AddRelativeInterrupt at /usr/src/debug/hatari-1.6.2/src/cycInt.c:338 #6 Video_InterruptHandler_EndLine at /usr/src/debug/hatari-1.6.2/src/video.c:1821 #7 m68k_run_1 at /usr/src/debug/hatari-1.6.2/src/uae-cpu/newcpu.c:1776 #8 m68k_go at /usr/src/debug/hatari-1.6.2/src/uae-cpu/newcpu.c:1872
Created attachment 691762 [details] File: backtrace
Created attachment 691763 [details] File: cgroup
Created attachment 691764 [details] File: core_backtrace
Created attachment 691765 [details] File: dso_list
Created attachment 691766 [details] File: environ
Created attachment 691767 [details] File: limits
Created attachment 691768 [details] File: maps
Created attachment 691769 [details] File: open_fds
Created attachment 691770 [details] File: proc_pid_status
Created attachment 691771 [details] File: var_log_messages
Can you please test hatari v1.7.0 and tell me if this bug shows again? It should be available very soon in updates-testing yum install hatari --enablerepo=updates-testing Thanks!
I've been trying to reproduce this crash with 1.6.2, but I didn't succeed. As far as I remember, this crash just suddenly happened, and not in a certain situation. Anyway, I'll try 1.7.0 (as soon as it is available) and see if I still can't reproduce this crash :-/
I've tested 1.7.0 and haven't seen anything strange. Can't say if this issue is fixed though, so I'll leave it up to you to determine what to do.
Because you are unable to reproduce the issue I close the bug. Please reopen if you'll reproduce it again.