This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug symtab/16405] backtrace locks up on Fedora 20
- From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 07 Jan 2014 20:30:46 +0000
- Subject: [Bug symtab/16405] backtrace locks up on Fedora 20
- Auto-submitted: auto-generated
- References: <bug-16405-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16405
Jan Kratochvil <jan.kratochvil at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jan.kratochvil at redhat dot com
Summary|call-sites lock up |backtrace locks up on
|backtrace on Fedora 20 |Fedora 20
--- Comment #1 from Jan Kratochvil <jan.kratochvil at redhat dot com> ---
call-sites are really innocent, it is DWARF expansion problem in general.
I have patched out call-sites in GDB code and the problem remains.
#0 in start_subfile
#1 in dwarf2_start_subfile
#2 in dwarf_decode_lines
#3 in handle_DW_AT_stmt_list
#4 in read_file_scope
#5 in process_die
#6 in process_full_comp_unit
#7 in process_queue
#8 in dw2_do_instantiate_symtab
#9 in dw2_instantiate_symtab
#10 in dw2_find_pc_sect_symtab
#11 in find_pc_sect_symtab
#12 in blockvector_for_pc_sect
#13 in block_for_pc_sect
#14 in block_for_pc
#15 in inline_frame_sniffer
#16 in frame_unwind_find_by_frame
#17 in compute_frame_id
#18 in get_prev_frame_if_no_cycle
#19 in get_prev_frame_1
#20 in get_prev_frame
#21 in value_of_dwarf_reg_entry
#22 in value_of_dwarf_block_entry
#23 in loclist_read_variable_at_entry
#24 in read_frame_arg
#25 in print_frame_args
#26 in print_frame
#27 in print_frame_info
#28 in backtrace_command_1
#29 in backtrace_command
--
You are receiving this mail because:
You are on the CC list for the bug.