public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: binutils@sourceware.org
Cc: Vsevolod Alekseyev <sevaa@sprynet.com>
Subject: bad patch - also not on list?
Date: Sun, 19 Nov 2023 23:22:07 -0700	[thread overview]
Message-ID: <87leatymeo.fsf@tromey.com> (raw)

I noticed that this commit:

commit b05efa39b47995db08c5537e4504271c8727702a
Author: Vsevolod Alekseyev <sevaa@sprynet.com>
Date:   Fri Nov 10 15:26:48 2023 +0000

    readelf..debug-dump=loc displays bogus base addresses
    
      PR 30880
      * dwarf.c (read_and_display_attr_value): Fix loclist handling. (display_loclists_list): Likewise.

... removes several hunks from display_gdb_index, causing readelf to be
incapable of reading v9 indices.

I think this was probably done in error.  However, I also could not find
this patch on the mailing list.  So, I wonder what's going in there.

I recommend reverting it.  However at the very least the regression
ought to be fixed.

thanks,
Tom

             reply	other threads:[~2023-11-20  6:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20  6:22 Tom Tromey [this message]
2023-11-20 14:32 ` Nick Clifton
2023-11-20 14:55   ` Vsevolod Alekseyev
2023-11-20 15:00   ` Tom Tromey
2023-11-20 16:09     ` Nick Clifton

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=87leatymeo.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=binutils@sourceware.org \
    --cc=sevaa@sprynet.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).