Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [gdb/testsuite] Add gdb.base/include-main.exp
Date: Wed, 1 Dec 2021 15:58:36 +0100	[thread overview]
Message-ID: <4e9e03b7-170f-4493-cd7e-0759357b8a43@suse.de> (raw)
In-Reply-To: <87k0gpuo30.fsf@tromey.com>

On 12/1/21 2:10 AM, Tom Tromey wrote:
> Tom> Given this, I wonder if we really want to continue supporting this.  I
> Tom> think it may be better to just declare these as compiler bugs (including
> Tom> gdb.ada/dgopt.exp) when using fission.
> 

I still don't understand what specific compiler behavior you consider a bug.

> Well, it so happens that my patches fix the dgopt.exp fission cases with
> my branch (but not the include-main.exp fission cases).  I was thinking
> maybe I'd be able to drop these patches, but they're also needed for
> plain include-main.exp on the branch.  So I think we can just carry on
> as-is, since I don't think the new reader will regress anything now, and
> the new patches aren't really that intrusive.

OK, that sounds good :)

FYI, I've now debugged the fission failure of include-main.exp on trunk,
and found that it's because dw2_get_file_names uses a cutu reader
constructor that ignores the dwo file.  By using the other constructor,
the test passes:
...
diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c
index 57538fc0adf..04c258d1aef 100644
--- a/gdb/dwarf2/read.c
+++ b/gdb/dwarf2/read.c
@@ -3084,7 +3084,7 @@ dw2_get_file_names (dwarf2_per_cu_data *this_cu,
   if (this_cu->v.quick->files_read)
     return this_cu->v.quick->file_names;

-  cutu_reader reader (this_cu, per_objfile);
+  cutu_reader reader (this_cu, per_objfile, nullptr, nullptr, false);
   if (!reader.dummy_p)
     dw2_get_file_names_reader (&reader, reader.comp_unit_die);

...

I'm testing this currently.

Thanks,
- Tom

  reply	other threads:[~2021-12-01 14:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26  9:48 Tom de Vries via Gdb-patches
2021-11-26 16:20 ` Simon Marchi
2021-11-26 17:11   ` Tom de Vries via Gdb-patches
2021-11-26 18:47     ` Simon Marchi
2021-11-27  0:59       ` Simon Marchi via Gdb-patches
2021-11-27  6:12         ` [committed][gdb/testsuite] Fix FAIL in gdb.base/list-missing-source.exp Tom de Vries via Gdb-patches
2021-11-30 20:39 ` [PATCH] [gdb/testsuite] Add gdb.base/include-main.exp Tom Tromey
2021-12-01  1:10   ` Tom Tromey
2021-12-01 14:58     ` Tom de Vries via Gdb-patches [this message]
2021-12-01 17:27       ` Tom Tromey
2021-12-02 12:59         ` Tom de Vries via Gdb-patches

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=4e9e03b7-170f-4493-cd7e-0759357b8a43@suse.de \
    --to=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.com \
    /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