On 2017.03.12 at 23:05 +0100, Mark Wielaard wrote: > While integrating the d_printing recursion guard change into gdb I > noticed we forgot to initialize the demangle_component d_printing > field in cplus_demangle_fill_{name,extended_operator,ctor,dtor}. > As is done in cplus_demangle_fill_{component,builtin_type,operator}. > It happened to work because in gcc all demangle_components were > allocated through d_make_empty. But gdb has its own allocation > mechanism (as might other users).
Nick has synced the binutils-gdb repro with gcc's. I think you should commit your fix as obvious. And it would be nice if Nick could sync again, after your patch went in. -- Markus