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
module top(output [1:0] o);
for (genvar i = 0; i < 4; i++) begin: B
reg [1:0] r;
always begin
r = 2'(i);
end
end
assign o = B[0].r;
endmodule
valgrind memcheck shows a use-after-free issue.
As far as I can tell from the memcheck report and the debug trace, it looks like the unroller, when finished, deletes the 'for' node, but a later traversal then reaches something that was deleted.
This also shows up with verilator_bin_dbg, with better quality source info, but it needs --no-debug-leak.
The text was updated successfully, but these errors were encountered:
Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2019-01-05T11:32:46Z
This is caused by the B[0] reference, but that's supported the code valgrind sees is actually looking for interfaces so the mis-reference is unlikely to cause real problems. Fix is non-trivial but will get to it shortly.
Author Name: Al Grant
Original Redmine Issue: 1386 from https://www.veripool.org
Original Assignee: Wilson Snyder (@wsnyder)
valgrind memcheck shows a use-after-free issue.
As far as I can tell from the memcheck report and the debug trace, it looks like the unroller, when finished, deletes the 'for' node, but a later traversal then reaches something that was deleted.
This also shows up with verilator_bin_dbg, with better quality source info, but it needs --no-debug-leak.
The text was updated successfully, but these errors were encountered: