From: Neeraj Singh <nksingh85@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
binutils@sourceware.org
Subject: Re: [BUG Report] objdump on mingw64 does not display debug_rnglists properly
Date: Tue, 30 Nov 2021 11:21:09 -0800 [thread overview]
Message-ID: <CANQDOdcnfffTdVdx44fejsCpmAsHFxZ4s2wws5GJDFnchzkCOA@mail.gmail.com> (raw)
In-Reply-To: <e60ee42c-3060-0dc2-cbdd-9c855520433a@redhat.com>
On Tue, Nov 30, 2021 at 9:40 AM Nick Clifton <nickc@redhat.com> wrote:
>
> Hi Johannes,
>
> > I believe that the binutils team prefers bug reports via
> > https://sourceware.org/bugzilla/, as per
> > https://www.gnu.org/software/binutils/.
>
> We do - and I really should have said this myself. Thanks for reminding us.
>
> > Would you mind opening a ticket there?
>
> As it happens I have already checked in a patch to fix the problem, but Neeraj
> does file a ticket I will update it with a link to the commit.
>
> Cheers
> Nick
>
I just sent mail to the overseers to get bugzilla access. Automated
account creation is currently disabled over there. If and when I get
an account, I can file a proper bug.
It looks like the display_debug_ranges issue with initial_length was
already fixed with
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=e7f024765a48fba4452535a5fc006a7e858730fd.
The bug exists in the 2.37 release of binutils.
Thanks,
Neeraj
prev parent reply other threads:[~2021-11-30 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 23:34 Neeraj Singh
2021-11-30 13:21 ` Nick Clifton
2021-11-30 13:36 ` Johannes Schindelin
2021-11-30 17:39 ` Nick Clifton
2021-11-30 19:21 ` Neeraj Singh [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=CANQDOdcnfffTdVdx44fejsCpmAsHFxZ4s2wws5GJDFnchzkCOA@mail.gmail.com \
--to=nksingh85@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).