-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VCS core dump #51
Comments
It's not something that we have seen yet. Realise that is not much help. |
I worked around for now. (By switching to DPI launch, rather than VPI) On Tue, Jul 9, 2013 at 4:03 PM, stuarthodgson notifications@github.com
|
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? |
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?) |
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= |
You don't need to see these in normal operation. cocotb#51
You don't need to see these in normal operation. cocotb#51
Trying in a different environment (Python 2.7.1 that appears to be statically linked only - no libpython2.7.so just libpython.2.7.a
and a recent version of VCS ( Compiler version G-2012.09-SP1-3_Full64; Runtime version G-2012.09-SP1-3_Full64; Jul 9 14:08 2013 )
Any thoughts on the cause of the Interpreter not initialized error. Seen this before at all?
The text was updated successfully, but these errors were encountered: