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 symtab/26327] GDB hangs in get_builder() due to recursive ancestor pointers Date: Fri, 07 May 2021 10:13:18 +0000 [thread overview] Message-ID: <bug-26327-4717-mTlu9jh5oH@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26327-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26327 --- Comment #16 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom de Vries <vries@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4cf88725da1cb503be04d3237354105ec170bc86 commit 4cf88725da1cb503be04d3237354105ec170bc86 Author: Tom de Vries <tdevries@suse.de> Date: Fri May 7 12:13:05 2021 +0200 [gdb/symtab] Fix infinite recursion in dwarf2_cu::get_builder() With the test-case attached in PR26327, gdb aborts: ... $ gdb -q -batch 447.dealII -ex "b main" Aborted (core dumped) ... when running out of stack due to infinite recursion: ... #8 0x00000000006aaba6 in dwarf2_cu::get_builder (this=0x35e4b40) at src/gdb/dwarf2/read.c:700 #9 0x00000000006aaba6 in dwarf2_cu::get_builder (this=0x22ee2c0) at src/gdb/dwarf2/read.c:700 #10 0x00000000006aaba6 in dwarf2_cu::get_builder (this=0x35e4b40) at src/gdb/dwarf2/read.c:700 #11 0x00000000006aaba6 in dwarf2_cu::get_builder (this=0x22ee2c0) at src/gdb/dwarf2/read.c:700 ... We're recursing in this code in dwarf2_cu::get_builder(): ... /* Otherwise, search ancestors for a valid builder. */ if (ancestor != nullptr) return ancestor->get_builder (); ... due to the fact that the ancestor chain is a cycle. Higher up in the call stack, we find some code that is responsible for triggering this, in new_symbol: ... case DW_TAG_formal_parameter: { /* If we are inside a function, mark this as an argument. If not, we might be looking at an argument to an inlined function when we do not have enough information to show inlined frames; pretend it's a local variable in that case so that the user can still see it. */ struct context_stack *curr = cu->get_builder ()->get_current_context_stack (); if (curr != nullptr && curr->name != nullptr) SYMBOL_IS_ARGUMENT (sym) = 1; ... This is code that was added to support pre-4.1 gcc, to be able to show arguments of inlined functions as locals, in the absense of sufficiently correct debug information. Removing this code (that is, doing SYMBOL_IS_ARGUMENT (sym) = 1 unconditially), fixes the crash. The ancestor variable also seems to have been added specifically to deal with fallout from this code, so remove that as well. Tested on x86_64-linux: - openSUSE Leap 15.2 with gcc 7.5.0, and - openSUSE Tumbleweed with gcc 10.3.0. gdb/ChangeLog: 2021-05-07 Tom de Vries <tdevries@suse.de> PR symtab/26327 * dwarf2/read.c (struct dwarf2_cu): Remove ancestor. (dwarf2_cu::get_builder): Remove ancestor-related code. (new_symbol): Remove code supporting pre-4.1 gcc that show arguments of inlined functions as locals. (follow_die_offset, follow_die_sig_1): Remove setting of ancestor. gdb/doc/ChangeLog: 2021-05-07 Tom de Vries <tdevries@suse.de> PR symtab/26327 * gdb.texinfo (Inline Functions): Update. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-05-07 10:13 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-31 23:54 [Bug symtab/26327] New: " d.c.ddcc at gmail dot com 2020-07-31 23:55 ` [Bug symtab/26327] " d.c.ddcc at gmail dot com 2020-07-31 23:59 ` d.c.ddcc at gmail dot com 2020-08-01 9:16 ` vries at gcc dot gnu.org 2020-08-01 12:52 ` simark at simark dot ca 2020-08-01 21:58 ` d.c.ddcc at gmail dot com 2020-08-01 22:02 ` d.c.ddcc at gmail dot com 2020-08-01 22:20 ` simark at simark dot ca 2020-10-19 12:21 ` vries at gcc dot gnu.org 2020-10-29 14:42 ` vries at gcc dot gnu.org 2020-11-07 21:43 ` d.c.ddcc at gmail dot com 2021-04-14 14:25 ` sourceware-bugzilla at mac dot mcrowe.com 2021-05-05 12:46 ` rguenth at gcc dot gnu.org 2021-05-05 12:49 ` rguenth at gcc dot gnu.org 2021-05-05 15:51 ` vries at gcc dot gnu.org 2021-05-05 16:59 ` vries at gcc dot gnu.org 2021-05-06 8:11 ` rguenth at gcc dot gnu.org 2021-05-06 12:16 ` vries at gcc dot gnu.org 2021-05-07 10:13 ` cvs-commit at gcc dot gnu.org [this message] 2021-05-07 10:14 ` vries at gcc dot gnu.org 2021-05-12 14:04 ` vries at gcc dot gnu.org 2021-05-21 16:13 ` giecrilj at stegny dot 2a.pl 2021-06-09 16:24 ` vries at gcc dot gnu.org 2021-06-16 10:44 ` cvs-commit at gcc dot gnu.org 2021-06-16 10:51 ` vries 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-26327-4717-mTlu9jh5oH@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).