Description of problem: Normal starting the debugger via eclipse kepler sr2, some breakpoints are set. Version-Release number of selected component: gdb-7.6.50.20130731-19.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gdb --interpreter mi2 --nx crash_function: find_pc_sect_psymtab executable: /usr/bin/gdb kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 find_pc_sect_psymtab at ../../gdb/psymtab.c:360 #1 find_pc_sect_symtab_from_partial at ../../gdb/psymtab.c:380 #2 find_pc_sect_symtab at ../../gdb/symtab.c:2168 #3 find_pc_symtab at ../../gdb/symtab.c:2185 #4 select_frame at ../../gdb/frame.c:1516 #5 get_selected_frame at ../../gdb/frame.c:1454 #6 print_thread_info at ../../gdb/thread.c:929 #7 mi_cmd_list_thread_groups at ../../gdb/mi/mi-main.c:881 #8 mi_cmd_execute at ../../gdb/mi/mi-main.c:2147 #9 captured_mi_execute_command at ../../gdb/mi/mi-main.c:1898
Created attachment 897906 [details] File: backtrace
Created attachment 897907 [details] File: cgroup
Created attachment 897908 [details] File: core_backtrace
Created attachment 897909 [details] File: dso_list
Created attachment 897910 [details] File: environ
Created attachment 897911 [details] File: exploitable
Created attachment 897912 [details] File: limits
Created attachment 897913 [details] File: maps
Created attachment 897914 [details] File: open_fds
Created attachment 897915 [details] File: proc_pid_status
Created attachment 897916 [details] File: var_log_messages
Another user experienced a similar problem: Starting debug session using Eclipse Kepler Service Release 2 ( DSF-Debugger ), no breakpoint was reached. Application size: 5.6MB, dynamically linked reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gdb --interpreter mi2 --nx crash_function: find_pc_sect_psymtab executable: /usr/bin/gdb kernel: 3.14.5-200.fc20.x86_64 package: gdb-7.7.1-13.fc20 reason: gdb killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.