projects / p5sagit/Function-Parameters.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 2c1cb7b)
don't double-free OPs on blead [#83439]
authorLukas Mai <l.mai@web.de>
Sat, 2 Mar 2013 23:19:59 +0000 (00:19 +0100)
committerLukas Mai <l.mai@web.de>
Sun, 3 Mar 2013 00:57:17 +0000 (01:57 +0100)
commited95eeff5007bb493b0eaa4827afc28f27466fb9
treeecc5c2380c935985d54f29d6d1223d505e284f1ftree | snapshot
parent2c1cb7bd2a76e09d6b6ebf18c5962f5d6722e49ccommit | diff
don't double-free OPs on blead [#83439]

Starting with 5.17.2 all newly allocated OPs are implicitly registered
with the current CV being compiled (PL_compcv). If an error is thrown
during compilation, these OPs are freed with the CV. This results in a
double-free if we also track and free OPs ourselves.

Solution: Check for this case and don't call op_free() in this
situation.
Parameters.xs diff | blob | blame | history
Unnamed repository; edit this file to name it for gitweb.