diff options
| author | mark <mark@138bc75d-0d04-0410-961f-82ee72b054a4> | 2017-03-13 18:26:47 +0000 |
|---|---|---|
| committer | Mark Wielaard <mark@klomp.org> | 2017-03-13 20:51:42 +0100 |
| commit | b9da89d161e3903faa335f444af2bf05e40f926e (patch) | |
| tree | 0fbdb729ff3259739ed1e64802cf9a25a641f26f /libiberty/ChangeLog | |
| parent | c793cac124dd2eb34042f2e43abb099a26e34cb0 (diff) | |
| download | gdb-b9da89d161e3903faa335f444af2bf05e40f926e.zip gdb-b9da89d161e3903faa335f444af2bf05e40f926e.tar.gz gdb-b9da89d161e3903faa335f444af2bf05e40f926e.tar.bz2 | |
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.
Diffstat (limited to 'libiberty/ChangeLog')
| -rw-r--r-- | libiberty/ChangeLog | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/libiberty/ChangeLog b/libiberty/ChangeLog index e93e327..b513fce 100644 --- a/libiberty/ChangeLog +++ b/libiberty/ChangeLog @@ -1,3 +1,11 @@ +2017-03-12 Mark Wielaard <mark@klomp.org> + + * 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. + 2017-03-08 Mark Wielaard <mark@klomp.org> PR demangler/70909 |