free some global objects even in the error case, in order to appease Valgrind

* If building with --enable-debug, we should always free all heap objects, even
  if they would be freed on program termination anway, so they
  won't appear as "possibly lost" in Valgrind.
  I had this missing if munged or evaled macro failed, which resulted in lots
  of false positives when running the testsuite under Valgrind.
* Also fixes possible crashes due to reusing already set GError variables.
  This could theoretically happen if a munged script terminates with ^C
  and its "quit" ED-hook would also throw any error.

0 files changed, 0 insertions, 0 deletions