public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nickc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/89394] libiberty :stack overflow in nm
Date: Wed, 06 May 2020 10:55:38 +0000	[thread overview]
Message-ID: <bug-89394-4-6CCouQEKsZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89394-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89394

--- Comment #10 from Nick Clifton <nickc at gcc dot gnu.org> ---
(In reply to Trupti Pardeshi from comment #9)
> May I know, in which version of binutils this fix is available?

2.35.  Which should be available in August, all being well.

Cheers
  Nick

PS.  The fix is already in the mainline development code, so you can always
clone the repository and build your own toolchain.

  parent reply	other threads:[~2020-05-06 10:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89394-4@http.gcc.gnu.org/bugzilla/>
2020-05-06  8:22 ` trupti_pardeshi at persistent dot co.in
2020-05-06 10:55 ` nickc at gcc dot gnu.org [this message]
2020-05-07 12:11 ` trupti_pardeshi at persistent dot co.in

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=bug-89394-4-6CCouQEKsZ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).