Description of problem: This typically happens to me after the following: Entering a "p" command and using tab completion on a symbol. On a large executable it takes a while, so sometimes I hit tab a second time thinking perhaps I didn't fully press the tab key. So GDB sees two tabs: the first completes the symbol on the command line and adds a space, then the second tab (I guess) tries to autocomplete from the universe. This tab takes way too long, obviously isn't what I intended, to I hit Control-C. I get a new GDB prompt. Then I enter the "p" command as I intended. And I get the SEGV. Version-Release number of selected component: gdb-7.6.1-42.fc19 Additional info: reporter: libreport-2.1.9 .gdb_history: backtrace_rating: 4 cmdline: gdb engine_test crash_function: lookup_objfile_from_block executable: /usr/bin/gdb kernel: 3.11.4-201.fc19.x86_64 runlevel: N 5 type: CCpp uid: 501 Truncated backtrace: Thread no. 0 (10 frames) #0 lookup_objfile_from_block at ../../gdb/symtab.c:1455 #1 lookup_symbol_global at ../../gdb/symtab.c:1780 #2 lookup_symbol_file at ../../gdb/cp-namespace.c:632 #3 cp_lookup_symbol_in_namespace at ../../gdb/cp-namespace.c:255 #4 lookup_namespace_scope at ../../gdb/cp-namespace.c:597 #5 cp_lookup_symbol_nonlocal at ../../gdb/cp-namespace.c:234 #6 lookup_symbol_aux at ../../gdb/symtab.c:1365 #7 lookup_symbol_in_language at ../../gdb/symtab.c:1211 #8 lookup_symbol at ../../gdb/symtab.c:1226 #9 lookup_typename at ../../gdb/gdbtypes.c:1254
Created attachment 821622 [details] File: backtrace
Created attachment 821623 [details] File: cgroup
Created attachment 821624 [details] File: core_backtrace
Created attachment 821625 [details] File: dso_list
Created attachment 821626 [details] File: environ
Created attachment 821627 [details] File: exploitable
Created attachment 821628 [details] File: limits
Created attachment 821629 [details] File: maps
Created attachment 821630 [details] File: open_fds
Created attachment 821631 [details] File: proc_pid_status
Created attachment 821632 [details] File: var_log_messages
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.