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/25886] [debug-types] FAIL: gdb.base/enumval.exp: p ZERO
Date: Tue, 28 Apr 2020 12:19:08 +0000	[thread overview]
Message-ID: <bug-25886-4717-AqwvA2xmuj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25886-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=25886

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> This patch fixes it:
> ...
> diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c
> index 82564edd7b2..fde2b595040 100644
> --- a/gdb/dwarf2/read.c
> +++ b/gdb/dwarf2/read.c
> @@ -10972,6 +10972,7 @@ dwarf2_cu::setup_type_unit_groups (struct die_info
> *die)
>                         COMPUNIT_DIRNAME (cust),
>                         compunit_language (cust),
>                         0, cust));
> +      list_in_scope = get_builder ()->get_file_symbols ();
>  
>        auto &file_names = line_header->file_names ();
>        for (i = 0; i < file_names.size (); ++i)
> ...

Which looks remarkably like the patch from PR24480 comment 4.

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

  parent reply	other threads:[~2020-04-28 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 11:53 [Bug symtab/25886] New: " vries at gcc dot gnu.org
2020-04-28 12:18 ` [Bug symtab/25886] " vries at gcc dot gnu.org
2020-04-28 12:19 ` vries at gcc dot gnu.org [this message]
2020-04-28 14:44 ` 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-25886-4717-AqwvA2xmuj@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).