Bug 906920

Summary: [abrt] hatari-1.6.2-2.fc18: CycInt_AddRelativeInterruptWithOffset: Process /usr/bin/hatari was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Roel van de Kraats <rhbug>
Component: hatariAssignee: Andrea Musuruane <musuruan>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: musuruan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e256e17eccdab6fa50496df6a3029d716eb7c0cb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-03 21:37:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Roel van de Kraats 2013-02-01 22:17:34 UTC 
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
Comment 1 Roel van de Kraats 2013-02-01 22:17:37 UTC 
Created attachment 691762 [details]
File: backtrace
Comment 2 Roel van de Kraats 2013-02-01 22:17:39 UTC 
Created attachment 691763 [details]
File: cgroup
Comment 3 Roel van de Kraats 2013-02-01 22:17:41 UTC 
Created attachment 691764 [details]
File: core_backtrace
Comment 4 Roel van de Kraats 2013-02-01 22:17:43 UTC 
Created attachment 691765 [details]
File: dso_list
Comment 5 Roel van de Kraats 2013-02-01 22:17:45 UTC 
Created attachment 691766 [details]
File: environ
Comment 6 Roel van de Kraats 2013-02-01 22:17:47 UTC 
Created attachment 691767 [details]
File: limits
Comment 7 Roel van de Kraats 2013-02-01 22:17:49 UTC 
Created attachment 691768 [details]
File: maps
Comment 8 Roel van de Kraats 2013-02-01 22:17:51 UTC 
Created attachment 691769 [details]
File: open_fds
Comment 9 Roel van de Kraats 2013-02-01 22:17:53 UTC 
Created attachment 691770 [details]
File: proc_pid_status
Comment 10 Roel van de Kraats 2013-02-01 22:17:55 UTC 
Created attachment 691771 [details]
File: var_log_messages
Comment 11 Andrea Musuruane 2013-06-29 12:14:20 UTC 
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!
Comment 12 Roel van de Kraats 2013-06-29 21:13:22 UTC 
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 :-/
Comment 13 Roel van de Kraats 2013-07-03 21:03:17 UTC 
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.
Comment 14 Andrea Musuruane 2013-07-03 21:37:21 UTC 
Because you are unable to reproduce the issue I close the bug. Please reopen if you'll reproduce it again.