public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/27893] [fission] segfault in dw2_expand_symtabs_matching_one Date: Fri, 30 Jul 2021 20:10:18 +0000 [thread overview] Message-ID: <bug-27893-4717-XeO1NYa4th@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27893-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27893 --- Comment #7 from Tom Tromey <tromey at sourceware dot org> --- queue_and_load_all_dwo_tus can seemingly create new type units even though it is called by dw2_do_instantiate_symtab - i.e., after the initial scan is done. So probably this code should either reallocate the symtab vector when doing this (may be expensive unless we can count how many additions there will be); or maybe the assert removed. This is pretty surprising to me, though I guess I don't really understand the DWO code. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-07-30 20:10 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-20 19:57 [Bug symtab/27893] New: " vries at gcc dot gnu.org 2021-05-20 23:03 ` [Bug symtab/27893] " vries at gcc dot gnu.org 2021-05-20 23:06 ` vries at gcc dot gnu.org 2021-05-20 23:29 ` vries at gcc dot gnu.org 2021-05-21 0:14 ` vries at gcc dot gnu.org 2021-05-21 0:45 ` vries at gcc dot gnu.org 2021-05-21 1:10 ` vries at gcc dot gnu.org 2021-07-30 20:10 ` tromey at sourceware dot org [this message] 2021-08-03 23:20 ` tromey at sourceware dot org 2021-08-15 19:38 ` tromey at sourceware dot org 2021-08-24 12:13 ` vries at gcc dot gnu.org 2021-08-24 14:03 ` cvs-commit at gcc dot gnu.org 2021-08-24 14:34 ` tromey at sourceware dot org 2021-09-08 21:04 ` cvs-commit at gcc dot gnu.org
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-27893-4717-XeO1NYa4th@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: linkBe 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).