public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27743] Internal error psymtab.c Date: Mon, 26 Apr 2021 15:40:53 +0000 [thread overview] Message-ID: <bug-27743-4717-cONcMBGS8J@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27743-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27743 --- Comment #24 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The gdb-10-branch branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e7d77ce0c408e7019f9885b8be64c9cdb46dd312 commit e7d77ce0c408e7019f9885b8be64c9cdb46dd312 Author: Tom Tromey <tromey@adacore.com> Date: Fri Apr 23 11:28:48 2021 -0600 Fix crash when expanding partial symtabs with DW_TAG_imported_unit PR gdb/27743 points out a gdb crash when expanding partial symtabs, where one of the compilation units uses DW_TAG_imported_unit. The bug is that partial_map_expand_apply expects only to be called for the outermost psymtab. However, filename searching doesn't (and probably shouldn't) guarantee this. The fix is to walk upward to find the outermost CU. A new test case is included. It is mostly copied from other test cases, which really sped up the effort. This bug does not occur on trunk. There, psym_map_symtabs_matching_filename is gone, replaced by psymbol_functions::expand_symtabs_matching. When this find a match, it calls psymtab_to_symtab, which does this same upward walk. Tested on x86-64 Fedora 32. I propose checking in this patch on the gdb-10 branch, and just the new test case on trunk. gdb/ChangeLog 2021-04-23 Tom Tromey <tromey@adacore.com> PR gdb/27743: * psymtab.c (partial_map_expand_apply): Expand outermost psymtab. gdb/testsuite/ChangeLog 2021-04-23 Tom Tromey <tromey@adacore.com> PR gdb/27743: * gdb.dwarf2/imported-unit-bp.exp: New file. * gdb.dwarf2/imported-unit-bp-main.c: New file. * gdb.dwarf2/imported-unit-bp-alt.c: New file. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-26 15:40 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-16 12:57 [Bug gdb/27743] New: " ilia.motornyi at jetbrains dot com 2021-04-16 13:12 ` [Bug gdb/27743] " ilia.motornyi at jetbrains dot com 2021-04-16 14:09 ` simark at simark dot ca 2021-04-16 14:31 ` ilia.motornyi at jetbrains dot com 2021-04-17 3:04 ` cn.yiki at gmail dot com 2021-04-17 13:06 ` simark at simark dot ca 2021-04-17 15:46 ` tromey at sourceware dot org 2021-04-18 4:56 ` cn.yiki at gmail dot com 2021-04-19 0:56 ` simark at simark dot ca 2021-04-19 0:56 ` simark at simark dot ca 2021-04-19 1:51 ` tromey at sourceware dot org 2021-04-19 1:54 ` simark at simark dot ca 2021-04-19 11:55 ` cn.yiki at gmail dot com 2021-04-19 14:04 ` ilia.motornyi at jetbrains dot com 2021-04-19 14:23 ` cn.yiki at gmail dot com 2021-04-19 14:41 ` ilia.motornyi at jetbrains dot com 2021-04-19 14:45 ` simark at simark dot ca 2021-04-19 14:46 ` simark at simark dot ca 2021-04-23 12:03 ` ilia.motornyi at jetbrains dot com 2021-04-23 12:54 ` ilia.motornyi at jetbrains dot com 2021-04-23 15:27 ` tromey at sourceware dot org 2021-04-23 15:34 ` tromey at sourceware dot org 2021-04-23 18:14 ` tromey at sourceware dot org 2021-04-23 18:23 ` tromey at sourceware dot org 2021-04-23 18:49 ` brobecker at gnat dot com 2021-04-26 15:39 ` cvs-commit at gcc dot gnu.org 2021-04-26 15:40 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-26 15:53 ` cvs-commit at gcc dot gnu.org 2021-04-26 15:55 ` tromey at sourceware dot 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-27743-4717-cONcMBGS8J@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).