UVM · Topic
UVM Debugging — Factory, Config & Connection Failures
Diagnosing the failures UVM produces rather than the DUT — factory overrides that did not apply, config_db misses, unconnected TLM ports and silent phase problems.
UVM failures rarely present as errors. An override that did not apply, a config_db set with the wrong scope string, or a TLM port that was never connected all produce a testbench that runs to completion and reports success, because the machinery that failed is the machinery that would have done the checking. That is why UVM debugging is mostly about making the framework state visible — printing the factory, dumping the config database, and checking connectivity — rather than about reading waveforms.