VCS core dump about cocotb HOT 5 CLOSED

It's not something that we have seen yet. Realise that is not much help.
Will have a think.

from cocotb.

I worked around for now. (By switching to DPI launch, rather than VPI)
—
Sent from Mailbox for iPhone

On Tue, Jul 9, 2013 at 4:03 PM, stuarthodgson [email protected]
wrote:

It's not something that we have seen yet. Realise that is not much help.

Will have a think.

Reply to this email directly or view it on GitHub:
#51 (comment)

from cocotb.

Gordon, I'm having trouble getting a stack trace from G2012.09 with the same options that give a trace on F-2011.12-SP1. Can you paste the command you used to get the trace for this issue?

from cocotb.

I think I ended up tracing this down to a mixup in python path and linked library - a peculiarity of the installed version here and how it is wrapped up, so the error actually makes sense:

Fatal Python error: Interpreter not initialized (version mismatch?)

from cocotb.

For future reference: the vcs command was

PYTHONPATH=/home/gmcgrego/co/cocotb/build/libs/x86_64:/home/gmcgrego/co/cocotb:/home/gmcgrego/co/cocotb/examples/demo:/libs/pylibs LD_LIBRARY_PATH=/home/gmcgrego/co/cocotb/build/libs/x86_64 MODULE=demo TESTCASE=
vcs -R +acc+1 +vpi -P pli.tab -sverilog -full64 -debug -load libgpi.so counter.v

from cocotb.