In a standard UVM testbench, what happens if a sequence raises an objection in its body() task, starts executing, but a fatal hardware error is injected causing the DUT to lock up, preventing the sequence from ever dropping the objection?
In UVM, the run phase relies purely on the objection mechanism to know when to conclude. If an objection is raised and never dropped (due to a lockup, dead loop, or deadlock), the phase will never terminate on its own, causing the simulation to hang indefinitely. An explicit timeout mechanism (like uvm_root::get().set_timeout()) must be configured to kill it.