You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Author Name: Johan Bjork
Original Redmine Issue: 1031 from https://www.veripool.org
Original Date: 2016-02-04
Original Assignee: Johan Bjork
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. phb/verilator-dev@2ac048d
The text was updated successfully, but these errors were encountered:
Author Name: Johan Bjork
Original Redmine Issue: 1031 from https://www.veripool.org
Original Date: 2016-02-04
Original Assignee: Johan Bjork
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.
phb/verilator-dev@2ac048d
The text was updated successfully, but these errors were encountered: