Description of problem: First running of software! Version-Release number of selected component: gnofract4d-3.14.1-4.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/python2 /usr/bin/gnofract4d crash_function: PyObject_Malloc executable: /usr/bin/python2.7 kernel: 3.15.10-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 PyObject_Malloc at /usr/src/debug/Python-2.7.5/Objects/obmalloc.c:784 #1 PyObject_Realloc at /usr/src/debug/Python-2.7.5/Objects/obmalloc.c:1182 #2 PyNode_AddChild at /usr/src/debug/Python-2.7.5/Parser/node.c:98 #3 push at /usr/src/debug/Python-2.7.5/Parser/parser.c:126 #4 PyParser_AddToken at /usr/src/debug/Python-2.7.5/Parser/parser.c:252 #5 parsetok at /usr/src/debug/Python-2.7.5/Parser/parsetok.c:198 #6 PyParser_ParseStringFlagsFilenameEx at /usr/src/debug/Python-2.7.5/Parser/parsetok.c:66 #7 PyParser_ASTFromString at /usr/src/debug/Python-2.7.5/Python/pythonrun.c:1467 #8 PyRun_StringFlags at /usr/src/debug/Python-2.7.5/Python/pythonrun.c:1334 #9 builtin_eval at /usr/src/debug/Python-2.7.5/Python/bltinmodule.c:695
Created attachment 928529 [details] File: backtrace
Created attachment 928530 [details] File: cgroup
Created attachment 928531 [details] File: core_backtrace
Created attachment 928532 [details] File: dso_list
Created attachment 928533 [details] File: environ
Created attachment 928534 [details] File: exploitable
Created attachment 928535 [details] File: limits
Created attachment 928536 [details] File: maps
Created attachment 928537 [details] File: open_fds
Created attachment 928538 [details] File: proc_pid_status
Created attachment 928539 [details] File: var_log_messages
The crash is in thread 1, inside PyObject_Malloc(), on this line: if ((pool->freeblock = *(block **)bp) != NULL) { Since bp == 0x3b, dereferencing it is not a great idea. A crash inside the memory allocation routines like this suggests memory corruption. Is this crash repeatable? If so, could you install the python-debug package and repeat whatever you do to cause the crash? You'll have to launch gnofract4d by running "python-debug /usr/bin/gnofract4d". If it is not repeatable, there's not much I can do. Whatever really went wrong happened some unknown amount of time before the actual crash.
Never mind, python-debug isn't going to help. It can't read compiled modules built for the optimized python build. We would have to build gnofract4d with python-debug. Still, is the crash repeatable?
gnofract4d-3.14.1-8.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/gnofract4d-3.14.1-8.fc20
gnofract4d-3.14.1-8.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/gnofract4d-3.14.1-8.fc21
Package gnofract4d-3.14.1-8.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gnofract4d-3.14.1-8.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-14800/gnofract4d-3.14.1-8.fc21 then log in and leave karma (feedback).
gnofract4d-3.14.1-8.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
gnofract4d-3.14.1-8.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.