Bug 1094971 - [abrt] naev: strcmp(): naev killed by SIGSEGV
Summary: [abrt] naev: strcmp(): naev killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: naev
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jonathan Dieter
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:59fdb04af583e869e464ca5fc45...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-06 19:30 UTC by Guillaume Poirier-Morency
Modified: 2015-06-30 01:28 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-30 01:28:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (70.27 KB, text/plain)
2014-05-06 19:30 UTC, Guillaume Poirier-Morency
no flags Details
File: cgroup (172 bytes, text/plain)
2014-05-06 19:30 UTC, Guillaume Poirier-Morency
no flags Details
File: core_backtrace (12.09 KB, text/plain)
2014-05-06 19:30 UTC, Guillaume Poirier-Morency
no flags Details
File: dso_list (5.88 KB, text/plain)
2014-05-06 19:30 UTC, Guillaume Poirier-Morency
no flags Details
File: environ (2.58 KB, text/plain)
2014-05-06 19:30 UTC, Guillaume Poirier-Morency
no flags Details
File: limits (1.29 KB, text/plain)
2014-05-06 19:30 UTC, Guillaume Poirier-Morency
no flags Details
File: maps (29.04 KB, text/plain)
2014-05-06 19:30 UTC, Guillaume Poirier-Morency
no flags Details
File: open_fds (102 bytes, text/plain)
2014-05-06 19:30 UTC, Guillaume Poirier-Morency
no flags Details
File: proc_pid_status (935 bytes, text/plain)
2014-05-06 19:30 UTC, Guillaume Poirier-Morency
no flags Details
File: var_log_messages (8.36 KB, text/plain)
2014-05-06 19:30 UTC, Guillaume Poirier-Morency
no flags Details

Description Guillaume Poirier-Morency 2014-05-06 19:30:18 UTC
Description of problem:
The game was saving automatically, but I ran out of disk space.

I've also lost my save and my backup: they've been replaced by empty files.

Version-Release number of selected component:
naev-0.5.3-4.fc19

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        naev
crash_function: strcmp
executable:     /usr/bin/naev
kernel:         3.13.10-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 strcmp at ../sysdeps/x86_64/strcmp.S:210
 #1 planet_exists at space.c:917
 #2 menu_main_bkg_system at menu.c:115
 #3 menu_main at menu.c:169

Comment 1 Guillaume Poirier-Morency 2014-05-06 19:30:24 UTC
Created attachment 892974 [details]
File: backtrace

Comment 2 Guillaume Poirier-Morency 2014-05-06 19:30:26 UTC
Created attachment 892975 [details]
File: cgroup

Comment 3 Guillaume Poirier-Morency 2014-05-06 19:30:28 UTC
Created attachment 892976 [details]
File: core_backtrace

Comment 4 Guillaume Poirier-Morency 2014-05-06 19:30:29 UTC
Created attachment 892977 [details]
File: dso_list

Comment 5 Guillaume Poirier-Morency 2014-05-06 19:30:31 UTC
Created attachment 892978 [details]
File: environ

Comment 6 Guillaume Poirier-Morency 2014-05-06 19:30:33 UTC
Created attachment 892979 [details]
File: limits

Comment 7 Guillaume Poirier-Morency 2014-05-06 19:30:39 UTC
Created attachment 892980 [details]
File: maps

Comment 8 Guillaume Poirier-Morency 2014-05-06 19:30:41 UTC
Created attachment 892981 [details]
File: open_fds

Comment 9 Guillaume Poirier-Morency 2014-05-06 19:30:43 UTC
Created attachment 892982 [details]
File: proc_pid_status

Comment 10 Guillaume Poirier-Morency 2014-05-06 19:30:45 UTC
Created attachment 892983 [details]
File: var_log_messages

Comment 11 Jonathan Dieter 2015-03-21 13:47:55 UTC
Can you please see if the bug still exists in 0.6.0?

Within the next day or two, you should be able to run:

yum --enable-repo=updates-testing update naev

to get it.

Comment 12 Guillaume Poirier-Morency 2015-05-08 22:34:19 UTC
(In reply to Jonathan Dieter from comment #11)
> Can you please see if the bug still exists in 0.6.0?
> 
> Within the next day or two, you should be able to run:
> 
> yum --enable-repo=updates-testing update naev
> 
> to get it.

This bug is hard to reproduce, you have any idea how I can try to simulate a full-disk?

Comment 13 Jonathan Dieter 2015-05-11 08:37:55 UTC
You could create a small (100MB) .img file, format it as ext4 and mount -oloop it at ~/.config/naev.  Fill it with a 99.9MB file and then see what happens.

Comment 14 Fedora End Of Life 2015-05-29 11:46:51 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Fedora End Of Life 2015-06-30 01:28:27 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.