Merge libiberty: Initialize d_printing in all cplus_demangle_fill_* functions.
authormark <mark@138bc75d-0d04-0410-961f-82ee72b054a4>
Mon, 13 Mar 2017 18:26:47 +0000 (18:26 +0000)
committerMark Wielaard <mark@klomp.org>
Mon, 13 Mar 2017 19:51:42 +0000 (20:51 +0100)
commitb9da89d161e3903faa335f444af2bf05e40f926e
tree0fbdb729ff3259739ed1e64802cf9a25a641f26f
parentc793cac124dd2eb34042f2e43abb099a26e34cb0
Merge libiberty: Initialize d_printing in all cplus_demangle_fill_* functions.

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).

libiberty/ChangeLog:

       * cp-demangle.c (cplus_demangle_fill_name): Initialize
       demangle_component d_printing.
       (cplus_demangle_fill_extended_operator): Likewise.
       (cplus_demangle_fill_ctor): Likewise.
       (cplus_demangle_fill_dtor): Likewise.

gdb/ChangeLog:

       * cp-name-parser.y (make_empty): Initialize d_printing to zero.
gdb/ChangeLog
gdb/cp-name-parser.y
libiberty/ChangeLog
libiberty/cp-demangle.c
This page took 0.024757 seconds and 4 git commands to generate.