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: Thu, 2 Dec 2021 13:59:11 +0100	[thread overview]
Message-ID: <bd46acd2-c583-1f62-53fe-9e065fd60cbe@suse.de> (raw)
In-Reply-To: <87fsrc6xsb.fsf@tromey.com>

On 12/1/21 6:27 PM, Tom Tromey wrote:
>> Given this, I wonder if we really want to continue supporting this.  I
>> think it may be better to just declare these as compiler bugs (including
>> gdb.ada/dgopt.exp) when using fission.
> 
> Tom> I still don't understand what specific compiler behavior you consider a bug.
> 
> The file name in the CU DIE does not appear in the line table.
> 

OK, it took me a while to understand, but I agree.

I was confused by a comment in the dwarf 5 standard:
...
Prior to DWARF Version 5, the current compilation file name was not
represented in the file_names field.
...
But that seems to be incorrect, there's an issue open to correct that (
https://dwarfstd.org/ShowIssue.php?issue=210713.1 ).

Anyway, with trunk gcc this no longer occurs, I've bisected the
difference to
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=96c82a16b2076891a9974d0f0e96a0b85fbc2df4
.

> Tom> FYI, I've now debugged the fission failure of include-main.exp on trunk,
> Tom> and found that it's because dw2_get_file_names uses a cutu reader
> Tom> constructor that ignores the dwo file.  By using the other constructor,
> Tom> the test passes:
> 
> I considered this, but when I looked, the .dwo file did not include the
> DW_AT_stmt_list.  So, I thought this would introduce other problems.
> 
> If this can work, then I think this is the only use of this constructor
> and so it could be removed.

I ran into regressions when testing this, so I filed a PR, mentioned the
tentative patch and a specific regression (
https://sourceware.org/bugzilla/show_bug.cgi?id=28644 ).

I'm parking this for the moment.

Thanks,
- Tom

      reply	other threads:[~2021-12-02 13:03 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
2021-12-01 17:27       ` Tom Tromey
2021-12-02 12:59         ` Tom de Vries via Gdb-patches [this message]

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=bd46acd2-c583-1f62-53fe-9e065fd60cbe@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