This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: https://sourceware.org/bugzilla/show_bug.cgi?id=23008
- From: Umesh Kalappa <umesh dot kalappa0 at gmail dot com>
- To: Michael Matz <matz at suse dot de>
- Cc: Nick Clifton <nickc at redhat dot com>, Binutils <binutils at sourceware dot org>
- Date: Tue, 22 Oct 2019 18:40:10 +0530
- Subject: Re: https://sourceware.org/bugzilla/show_bug.cgi?id=23008
- References: <CAGfacvSr=1+WzwbKJjH6vFLs5V29JNWuaubEgLNFb=CU5teFng@mail.gmail.com> <alpine.LSU.2.21.1910221242340.30048@wotan.suse.de>
Thank you Michael for the information.
Thats help.
~Umesh
On Tue, Oct 22, 2019 at 6:24 PM Michael Matz <matz@suse.de> wrote:
>
> Hi,
>
> On Tue, 22 Oct 2019, Umesh Kalappa wrote:
>
> > We are bit confused with the subjected issue as stated by you in the
> > last comment it's fixed in the gcc libiberty sources.
> >
> > But Michael states that , its the expected behavior with given input
> > (like many successive F's) .
> >
> > Please, can you brief us , what fix went into it?
>
> The "fix" in the demangler, if you want to call it that, is the
> introduction of an artificial limit on the nesting depth of templates,
> currently set to 2048. It's a combination of revisions r266886, r267020
> and r270258 in the GCC svn repo. The limit is active by default and you
> can disable it programmatically (and in objdump via -r).
>
> So, recent objdump won't segfault on such names (and that way it's a fix
> for script kiddie CVEs), but on the other hand won't demangle such
> symbols at all (in that way it's not fix).
>
>
> Ciao,
> Michael.