Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: "Alexandra Hájková" <ahajkova@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add dw2-aranges.exp
Date: Wed, 6 Nov 2024 11:58:18 -0700	[thread overview]
Message-ID: <20241106115712.2df7e54f@f40-zbm-amd> (raw)
In-Reply-To: <20241106163255.2619114-1-ahajkova@redhat.com>

Hi Sasha,

The actual patches in this commit LGTM (once Keith's concern is
addressed), but I'd like to see some changes to the commit log...

> This test tests GDB is able to load a file with the
> .debug_aranges section Address size set to 0.

Maybe say:

    This test checks that GDB is able to load DWARF information when
    .debug_aranges has a section address size that is set to 0.

> The test was originally written by Jan Kratochvil to test
> commit 927aa2e778dce440f4de5de8fc37ead1683a804e
> Author: Jan Kratochvil <jan.kratochvil@redhat.com>
> Date:   Fri Dec 8 22:44:12 2017 +0000
> 
>       DWARF-5: .debug_names index consumer

I think that this can be written more compactly, perhaps like this:

    This test was originally written by Jan Kratochvil to test commit
    927aa2e778d from 2017, titled "DWARF-5:  .debug_names index
    consumer".

> The test was passing from the beginning.
> This test has been living in the Fedora tree
> for a long time, it seems to be a reasonable
> some bad debug information.

Maybe change this to:

    This test was originally written using a static .S file and has
    been present in the Fedora tree for a long time.

> If dwarf2/aranges.c is modified to turn off the
> address_size check, GDB will crash with SIGPE

s/SIGPE/SIGFPE/

(I think.)

> when loading the executable with the address size

s/the address/address/

> set to zero.
> 
> I modified the DWARF assembler to make it possible
> to set the Addres size to zero in a .debug_aranges section

s/Addres/address/

> and used a DWARF assembler to produce the assembly file.

s/a DWARF/the DWARF/

With those changes (assuming you're okay with them) and with
Keith's change to use "require dwarf2_support",...

Approved-by: Kevin Buettner <kevinb@redhat.com>


  parent reply	other threads:[~2024-11-06 18:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06 16:32 Alexandra Hájková
2024-11-06 17:58 ` Keith Seitz
2024-11-06 18:58 ` Kevin Buettner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-06 16:31 Alexandra Hájková

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=20241106115712.2df7e54f@f40-zbm-amd \
    --to=kevinb@redhat.com \
    --cc=ahajkova@redhat.com \
    --cc=gdb-patches@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