Hi Tim, On Sun, Jun 14, 2020 at 12:37:43AM +0200, Tim Duesterhus wrote: > Willy, > > careful with this one: I don't know whether it's safe to simply free the > expression there or whether I need to somehow check whether there actually > is some expression. > > It does not crash with my stupid example configuration showcasing the leak, > but of course real world configurations might or might not trigger a bogus > free there.
It seems to be OK. I was worried that the pointer could be part of a union containing either the expression or its text version during parsing, but this doesn't seem to be the case, so apparently it's OK to always free it if it appears in a rule. Thanks! Willy
