public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/16405] backtrace locks up on Fedora 20
Date: Tue, 07 Jan 2014 20:30:00 -0000 [thread overview]
Message-ID: <bug-16405-4717-rR7q7H0SZ3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16405-4717@http.sourceware.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.
next prev parent reply other threads:[~2014-01-07 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 18:16 [Bug symtab/16405] New: call-sites lock up backtrace " jan.kratochvil at redhat dot com
2014-01-07 20:30 ` jan.kratochvil at redhat dot com [this message]
2014-01-10 20:49 ` [Bug symtab/16405] backtrace locks up " jan.kratochvil at redhat dot com
2014-01-10 20:50 ` [Bug symtab/16405] backtrace takes GBs and minutes with dwz -m jan.kratochvil at redhat dot com
2014-05-05 21:42 ` mjw at redhat dot com
2014-10-01 18:24 ` jan.kratochvil at redhat dot com
2014-10-01 19:49 ` jan.kratochvil at redhat dot com
2014-10-06 17:58 ` sergiodj at redhat dot com
2015-01-24 15:03 ` jan.kratochvil at redhat dot com
2015-01-25 15:33 ` jan.kratochvil at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-16405-4717-rR7q7H0SZ3@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).