Hide Forgot
Description of problem: seems to just randomly crash Version-Release number of selected component: gdb-7.6.1-46.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: gdb -batch -ex 'set debug-file-directory /' -ex 'file /usr/bin/python2.7' -ex 'core-file ./coredump' -ex 'thread apply all backtrace 1024 full' -ex 'info sharedlib' -ex 'print (char*)__abort_msg' -ex 'print (char*)__glib_assert_msg' -ex 'info all-registers' -ex disassemble crash_function: elf_symtab_read executable: /usr/bin/gdb kernel: 3.11.10-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 0 var_log_messages: Binary file /var/log/messages matches Truncated backtrace: Thread no. 1 (10 frames) #0 elf_symtab_read at ../../gdb/elfread.c:263 #1 elf_symfile_read at ../../gdb/elfread.c:2320 #2 read_symbols at ../../gdb/symfile.c:827 #3 syms_from_objfile_1 at ../../gdb/symfile.c:1027 #4 syms_from_objfile at ../../gdb/symfile.c:1045 #5 symbol_file_add_with_addrs_or_offsets at ../../gdb/symfile.c:1144 #6 symbol_file_add_from_bfd at ../../gdb/symfile.c:1234 #7 solib_read_symbols at ../../gdb/solib.c:608 #8 solib_add at ../../gdb/solib.c:937 #9 post_create_inferior at ../../gdb/infcmd.c:459
Created attachment 836860 [details] File: backtrace
Created attachment 836861 [details] File: cgroup
Created attachment 836862 [details] File: core_backtrace
Created attachment 836863 [details] File: dso_list
Created attachment 836864 [details] File: environ
Created attachment 836865 [details] File: exploitable
Created attachment 836866 [details] File: limits
Created attachment 836867 [details] File: maps
Created attachment 836868 [details] File: open_fds
Created attachment 836869 [details] File: proc_pid_status
You should have in /var/spool/abrt a different crash of /usr/bin/python2.7. There should be file 'coredump'. There you should be able to run the 'cmdline' command-line in Comment 0 above. This should make the crash reproducible. (Then it would be best to send the 'coredump' file but that's next step.)
The needed file is: /var/tmp/abrt/ccpp-2013-12-15-01:08:21-11115/coredump (found in environ) Sure it may contain security information of the python process.
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.