Use new/delete instead of malloc/free-based functions
authorSimon Marchi <simon.marchi@polymtl.ca>
Thu, 1 Dec 2016 02:41:46 +0000 (21:41 -0500)
committerSimon Marchi <simon.marchi@polymtl.ca>
Thu, 1 Dec 2016 02:41:46 +0000 (21:41 -0500)
commit5486f16481dffa1c1a0d1fd9e38b97e3678078ed
tree611960588a1a7b491804f07f3fb10a2597ba45b8
parent5084b13657023904cb60737abdf4cefb539a5fc4
Use new/delete instead of malloc/free-based functions

The following patches introduce C++ vectors and strings as fields of the
various ui_out structures.  We therefore need to use new/delete so that
their contructor/destructor is called.  I find it simpler to change all
the allocations in a separate preliminary patch, rather than in each
individual patch.

gdb/ChangeLog:

* cli-out.c (cli_uiout_dtor): Use delete instead of xfree.
(cli_out_new): Use new instead of XNEW.
* mi/mi-out.c (mi_out_data_dtor): Use delete instead of xfree.
(mi_out_new): Use new instead of XNEW.
* tui/tui-out.c (tui_out_new): Likewise.
* ui-out.c (push_level): Likewise.
(pop_level): Use delete instead of xfree.
(clear_header_list): Use delete instead of xfree.
(append_header_to_list): Use new instead of XNEW.
(ui_out_new): Likewise.
gdb/ChangeLog
gdb/cli-out.c
gdb/mi/mi-out.c
gdb/tui/tui-out.c
gdb/ui-out.c