]> git.ipfire.org Git - thirdparty/gcc.git/commit - libiberty/cp-demangle.c
libiberty: Limit demangler maximum d_print_comp recursion call depth.
authorMark Wielaard <mark@klomp.org>
Fri, 21 Apr 2017 09:02:03 +0000 (09:02 +0000)
committerMark Wielaard <mark@gcc.gnu.org>
Fri, 21 Apr 2017 09:02:03 +0000 (09:02 +0000)
commit6b086d35b79425de90a09c8bd843170a038fbde8
tree8229f4b0678829d2f4ee36ac3f394bc4b2c195cb
parent13b6ef76dc275232310ebfca27db08aeef9b858c
libiberty: Limit demangler maximum d_print_comp recursion call depth.

The fix for PR demangler/70909 and 67264 (endless demangler recursion)
catches when a demangle_component is printed in a cycle. But that doesn't
protect the call stack blowing up from non-cyclic nested types printed
recursively through d_print_comp. This can happen by a (very) long mangled
string that simply creates a very deep pointer or qualifier chain. Limit
the recursive d_print_comp call depth for a d_print_info to 1K nested
types.

libiberty/ChangeLog:

        * cp-demangle.c (MAX_RECURSION_COUNT): New constant.
        (struct d_print_info): Add recursion field.
        (d_print_init): Initialize recursion.
        (d_print_comp): Check and update d_print_info recursion depth.

From-SVN: r247056
libiberty/ChangeLog
libiberty/cp-demangle.c