Bug 568680

Summary: [abrt] crash in teeworlds-0.5.2-2.fc12: Process /usr/bin/teeworlds was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: slidercrank <pinode>
Component: teeworldsAssignee: Thomas Kowaliczek <linuxdonald>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: linuxdonald, lkundrak
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:ad2b73863708270fdf7746562176b401eb17ca33
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-08 11:40:09 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

Description slidercrank 2010-02-26 11:02:22 UTC 
abrt 1.0.7 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: teeworlds
component: teeworlds
executable: /usr/bin/teeworlds
kernel: 2.6.31.12-174.2.22.fc12.i686.PAE
package: teeworlds-0.5.2-2.fc12
rating: 4
reason: Process /usr/bin/teeworlds was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 slidercrank 2010-02-26 11:02:26 UTC 
Created attachment 396510 [details]
File: backtrace
Comment 2 Lubomir Rintel 2010-02-26 11:26:20 UTC 
331         if(config.cl_predict && client_state() != CLIENTSTATE_DEMOPLAYBACK)
332         {
333                 if(!snap.local_character || (snap.local_character->health < 0) || (snap.gameobj && snap.gameobj->game_over))
334                 {
335                         // don't use predicted
336                 }

I can't tell whether another thread could have null-ed snap.local_character or snap.gameobj during the evaluation of the conditional or they had invalid values before.

I'm wondering if you can reproduce the issue or provide more details about how did the crash happen?
Comment 3 slidercrank 2010-02-26 11:36:50 UTC 
> I'm wondering if you can reproduce the issue or provide more details about how
> did the crash happen?    

I doubt I can reproduce it. I was playing and the vote to change map was passed. So after a new map was loaded I expected a game to start on the new map but it crashed instead.
So it happened right after the map was loaded but before the map was shown on the screen.
Comment 4 Thomas Kowaliczek 2010-03-07 15:25:30 UTC 
any new news about that here?
Comment 5 slidercrank 2010-03-07 15:38:09 UTC 
no news. the bug is hardly reproducible. it happened only once. so I can't help with it.
Comment 6 Lubomir Rintel 2010-03-08 11:40:09 UTC 
I'm afraid I don't have enough information to be able to do anything about this :(
Closing.

Thank you for the report anyway.