read-after-free in V3Scope
Ran valgrind on verilator to try and figure out a strange crash. Found this (unrelated to the crash) issue.
In V3Scope when cleaning up cloned nodes, it's possible that the visitor first finds and deletes a cloned V3Task, then later the visitor hits a V3TaskRef referencing the deleted task and accesses free'd memory. https://github.com/phb/verilator-dev/commit/2ac048df503bf09c81f4eeab2e7638ea8ecb5337
Also available in: Atom