In reply to dave_59:
Hi dave,
I tried with the below code
ork : fork_block
begin: begin_block
fork
task1;
join_none
for (;;) begin : for_loop
fork
task2;
join_none
end : for_loop
fork
task3;
join_none
@reset_event disable fork;
end : begin_block
join : join_block
somehow the simulation is hanged.
I can see issue is driver getting not stopped
here is the difference between passing and failing logs. failing log is not giving those messages and passing log is giving the messages and continuing further. I guess failing log is waiting for them to get stopped. I am not sure how the disable fork_drivepkt is avoiding the issue. Could you please clarify what is the difference between disable fork and disable fork_name. what could be the possible reason for the simulation to work with disable fork_name
messages in passing log are as follows.
Driver(0) Stop requested
Driver(0) 0 out of 1 threads have now stopped
1 out of 1 threads have now stopped
Driver(0) Stopped
the reset_event is triggered during the stop_xactor call of this driver.I wanted to stop the all xactors but the tasks are not getting stopped.I needed to disable them manually with simple solution.it seems reset xactor will kill them all without disabling them manually.