Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Martin Simmons <qqxnjvamvxwx@dyxyl.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][PR symtab/32658] Fix parsing .debug_aranges section for MIPS signed addresses
Date: Wed, 19 Mar 2025 10:48:09 -0600	[thread overview]
Message-ID: <87tt7pj7au.fsf@tromey.com> (raw)
In-Reply-To: <20250307235722.1D4CDEE05D@localhost.localdomain> (Martin Simmons's message of "Fri, 7 Mar 2025 23:57:22 +0000 (GMT)")

>>>>> "Martin" == Martin Simmons <qqxnjvamvxwx@dyxyl.com> writes:

Martin> This patch fixes https://sourceware.org/bugzilla/show_bug.cgi?id=32658 by sign

There should be a 'Bug: ...' trailer in the comment with this link.

FWIW I see now that other spots in the DWARF reader do use the BFD
approach:

  int signed_addr_p = bfd_get_sign_extend_vma (objfile->obfd.get ());

Martin> I made it explicitly sign extend the addresses after they are read
Martin> (instead of using extract_signed_integer) because I don't know if the
Martin> address_size in the section will always be equal to the gdb arch_size.

I don't think this should be a concern, unless you have an example where
it actually happens.

The .debug_aranges header spec explicitly says "size of an address in
bytes on the target architecture".

Tom

  parent reply	other threads:[~2025-03-19 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 23:57 Martin Simmons
2025-03-08 16:39 ` Tom Tromey
2025-03-09 20:40   ` {Spam?} " Martin Simmons
2025-03-19 16:42     ` Tom Tromey
2025-03-19 16:48 ` Tom Tromey [this message]
2025-03-27 16:03   ` [PATCH v2][PR " Martin Simmons
2025-04-03 15:03     ` Tom Tromey

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=87tt7pj7au.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qqxnjvamvxwx@dyxyl.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