Red Hat Bugzilla – Bug 1007127
[abrt] tuxmath-2.0.1-4.fc19: __strlen_sse2: Process /usr/bin/tuxmath was killed by signal 11 (SIGSEGV)
Last modified: 2015-02-18 06:26:46 EST
Description of problem:
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (9 frames)
#0 __strlen_sse2 at ../sysdeps/x86_64/strlen.S:31
#1 __strdup at strdup.c:41
#2 read_named_config_file at fileops.c:332
#3 run_academy at menu.c:259
#4 handle_activity at menu.c:142
#5 T4K_RunMenu at t4k_menu.c:933
#6 run_menu at menu.c:111
#7 RunMainMenu at menu.c:755
#8 TitleScreen at titlescreen.c:306
Created attachment 796586 [details]
Created attachment 796587 [details]
Created attachment 796588 [details]
Created attachment 796589 [details]
Created attachment 796590 [details]
Created attachment 796591 [details]
Created attachment 796592 [details]
Created attachment 796593 [details]
Created attachment 796594 [details]
Created attachment 796595 [details]
Is there any particular type of game or activity that triggers this?
My apologies for the delay.
I just got it to crash by the following process:
- Used the games menu to pick a couple of different addition games (sums to 15, adding positives to negatives), navigating back and forth through the games menu between sessions; both game sessions completed successfully
- Played Factoroids once, game ended abruptly (Enter on numeric keypad was pressed)
- Played Factoroids again, again the game ended when the numeric keypad's Enter key was pressed
- Played Factoroids a third time; used "D" to change the prime number; used up/down to move the ship much more than in previous games
ABRT is in the process of creating a new crash report; I will cross-reference it here if the duplication is not detected.
NOTE: My son also reports that it will consistently crash playing "Math Command Fleet Missions", and we think that may be related to the initial report.
Hope this helps!
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Thank you for reporting this bug and we are sorry it could not be fixed.