Version-Release number of selected component: anjuta-3.4.4-1.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: anjuta crash_function: debugger_abort kernel: 3.6.5-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 debugger_abort at debugger.c:1960 : #1 idebugger_abort at plugin.c:552 : #2 dma_command_run at command.c:1144 : #3 dma_debugger_queue_execute at queue.c:402 : #4 dma_debugger_queue_append at queue.c:718 : #8 g_signal_emit_by_name at gsignal.c:3393 : #9 anjuta_shell_session_save at anjuta-shell.c:903 : #10 project_manager_save_session at plugin.c:138 : #14 g_signal_emit_by_name at gsignal.c:3393 : #15 anjuta_shell_notify_exit at anjuta-shell.c:959
Created attachment 647078 [details] File: core_backtrace
Created attachment 647079 [details] File: environ
Created attachment 647080 [details] File: limits
Created attachment 647081 [details] File: backtrace
Created attachment 647082 [details] File: cgroup
Created attachment 647083 [details] File: smolt_data
Created attachment 647084 [details] File: xsession_errors
Created attachment 647085 [details] File: executable
Created attachment 647086 [details] File: maps
Created attachment 647087 [details] File: dso_list
Created attachment 647088 [details] File: proc_pid_status
Created attachment 647089 [details] File: open_fds
Created attachment 647090 [details] File: var_log_messages
Could you give some info how to reproduce this bug? Thanks!
(In reply to comment #14) > Could you give some info how to reproduce this bug? Thanks! I don't think this is possible because the program crashed unexpectedly. Maybe it is related to another crash: https://bugzilla.redhat.com/show_bug.cgi?id=877708
(In reply to comment #15) > (In reply to comment #14) > > Could you give some info how to reproduce this bug? Thanks! > > I don't think this is possible because the program crashed unexpectedly. > Maybe it is related to another crash: > https://bugzilla.redhat.com/show_bug.cgi?id=877708 Sorry, the right link is https://bugzilla.redhat.com/show_bug.cgi?id=877709
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.