Marlon James

Pinging @AndrewNolte.

You can take a look at Verilator and how they implement some of the VPI specification. If bluesim were to add an implementation of VPI to the simulator that supported...

I will try to take a look at this soon.

I'll take another look at this soon. Please don't merge until then.

It might be related to whatever the root cause of https://github.com/cocotb/cocotb/issues/3013 is.

pseudo-region support needs an overhaul in GPI.

@wsnyder We are passing `""` already: https://github.com/cocotb/cocotb/blob/ad1fe4883b2fc6f75682651fa31c53d161414a29/cocotb/share/lib/verilator/verilator.cpp#L54 For the `t_vpi_module` Verilator test, `Vt_vpi_module__Syms.cpp` sets up the scopes and hierarchy like so: ```cpp // Setup scopes __Vscope_t.configure(this, name(), "t", "t", -12,...

Somehow the `$display` blocks added to `sample_module.sv` in #2322 are causing this. https://github.com/cocotb/cocotb/blob/5d4ae7af2aa357dbb7d12fcb078732fbf40c4bfc/tests/designs/sample_module/sample_module.sv#L158-L166 If I remove them, everything works.

This appears to be back, shows up in `test_fatal`. See #3237

We could add a `Future` trigger that has access to both the `Outcome` and `RunningCoroutine` objects. Alternatively we could add a trigger that returns just the `RunningCoroutine` object, an alternate...