SystemVerilog OOP Mastery · All levels

Scenario: Shallow Copy Aliasing

A scoreboard intermittently compares expected and actual transactions as equal even when waveforms show divergence. Root-cause suspicion points to cloned objects mutating together through shared nested handles.

Scenario

A scoreboard intermittently compares expected and actual transactions as equal even when waveforms show divergence. Root-cause suspicion points to cloned objects mutating together through shared nested handles.

What to focus on

Unexpected correlation between expected and observed payload updates after enqueue, indicating aliasing of nested objects.

Common traps

  • Treating top-level clone success as proof that all nested handles are deep-copied.

  • Checking only top-level handle identity and missing nested object aliasing.

  • Adding compare exceptions instead of fixing copy contract ownership.

Related topics