public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries 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: Thu, 29 Oct 2020 14:42:48 +0000	[thread overview]
Message-ID: <bug-26327-4717-nrbFawrXbL@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 #7 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #6)
> Tentative patch, prevents introducing cycles in ancestor chain:

Which fixes the hang.  But not the "./gdb -nx -readnow 447.dealII" crash.

This fixes the crash:
...
diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c
index e1c528f44d..64f2ba0ee0 100644
--- a/gdb/dwarf2/read.c
+++ b/gdb/dwarf2/read.c
@@ -21632,15 +21632,7 @@ new_symbol (struct die_info *die, struct type *type,
struct dwarf2
_cu *cu,
          break;
        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;
+           SYMBOL_IS_ARGUMENT (sym) = 1;
            attr = dwarf2_attr (die, DW_AT_location, cu);
            if (attr != nullptr)
              {
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-10-29 14:42 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 [this message]
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
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-nrbFawrXbL@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).