Version-Release number of selected component: gdb-7.4.50.20120120-50.fc17 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 backtrace_rating: 4 cmdline: gdb --interpreter mi2 --nx crash_function: xcalloc kernel: 3.5.4-2.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #3 xcalloc at ../../gdb/common/common-utils.c:90 : #4 serial_fdopen_ops at ../../gdb/serial.c:283 : #6 print_flush at ../../gdb/exceptions.c:281 : #7 exception_print at ../../gdb/exceptions.c:332 : #8 start_event_loop at ../../gdb/event-loop.c:494 : #9 captured_command_loop at ../../gdb/main.c:234 : #10 catch_errors at ../../gdb/exceptions.c:546 : #11 captured_main at ../../gdb/main.c:1095 : #12 catch_errors at ../../gdb/exceptions.c:546 : #13 gdb_main at ../../gdb/main.c:1105
Created attachment 630990 [details] File: core_backtrace
Created attachment 630991 [details] File: environ
Created attachment 630992 [details] File: backtrace
Created attachment 630993 [details] File: limits
Created attachment 630994 [details] File: cgroup
Created attachment 630995 [details] File: maps
Created attachment 630996 [details] File: dso_list
Created attachment 630997 [details] File: var_log_messages
Created attachment 630998 [details] File: open_fds
This is a weird backtrace, suggesting maybe memory corruption. Can you say what you were doing when this happened? Could we possibly get the gdb core file? I don't know if it would help, but it might.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.