Is there any good way to assert/enforce sequence creates new object when sending to sequencer?
When supporting in-house uvm vip, I often receive request from other users stating seeing issues with vip. Most time it turned out it's user's sequence problem where transaction is not being created each loop or same transaction handle is being used in multi-thread statement to create parallel RW scenario. And such usage will definitely mess up driver.
One way I can think of is to do deep copy upon receive transaction from SQR, but this seems expensive.
I'm curious is there any effective checks/assertions can be done to find these issues easier?
Thanks in advance.