[xmlroff] Fixing memory leaks

[Tony G. <Ton...@Su...>]

FYI, I've been running valgrind and fixing memory leaks, and for the
xmlroff currently in CVS, the memory lost when formatting 'xmlroff.fo'
is less than half what it was when I started.

Fixing memory leaks is something almost anyone can do: all it requires
is valgrind, a bit of patience, and a bit of C knowledge.  Memory leak
patches are more than welcome.

On the more ambitious side of things, it would be useful to modify
xmlroff.c so it can run the same input multiple times to show up the
leaks that increase versus those that are constant and to modify the
testing framework so it has an option to collect and compare valgrind
results.

Regards,


Tony.