Re: Fix some memory leaks in ecpg.addons

"Tristan Partin" <tristan(at)neon(dot)tech> writes:
> clang and gcc both now support -fsanitize=address,undefined. These are
> really useful to me personally when trying to debug issues.
> Unfortunately ecpg code has a ton of memory leaks, which makes builds
> really painful. It would be great to fix all of them, but I don't have
> the patience to try to read flex/bison code. Here are two memory leak
> fixes in any case.

I'm kind of failing to see the point. As you say, the ecpg
preprocessor leaks memory like there's no tomorrow. But given its
usage (process one source file and exit) I'm not sure that is worth
much effort to fix. And what does it buy to fix just two spots?

regards, tom lane