[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #56694] [PATCH] troff mixes malloc / delete[]
From: |
G. Branden Robinson |
Subject: |
[bug #56694] [PATCH] troff mixes malloc / delete[] |
Date: |
Tue, 1 Mar 2022 09:08:10 -0500 (EST) |
Follow-up Comment #2, bug #56694 (project groff):
commit 06ee2524421ae607d0310204e3ddaea790af2fd6
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date: Thu Oct 22 21:03:09 2020 +1100
Stop mixing up heap storage management strategies.
...in one respect, anyway. A further audit would be good.
Use only malloc() and free() to manage memory of paths opened by the
parser instead of mixing in C++ new/delete management under some
runtime-dependent circumstances.
* src/libs/libgroff/relocate.cpp (relocatep): Use malloc(), not new.
* src/roff/troff/input.cpp (process_macro_file, process_startup_file,
macro_source): Use free(), not (a_)delete.
Thanks to an anonymous contributor for the report and patch.
Fixes <https://savannah.gnu.org/bugs/index.php?56694>.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?56694>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #56694] [PATCH] troff mixes malloc / delete[],
G. Branden Robinson <=