-
Notifications
You must be signed in to change notification settings - Fork 27
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
Unix Signal SIGABRT raised from user application code #230
Comments
Interesting... Appreciate the report! If I'm understanding correctly, there are two situations in which the crash occurs:
Are you able to import and use PyVSC outside the simulation (ie in a standalone Python script from the Unix command line)? I'm wondering whether there is a conflict between PyVSC and your OS or between PyVSC and Xcelium. Can you share the stack trace? |
Yes, the crash occurs in both scenarios. I installed a fresh venv with Python 3.12.7 and with Python 3.10.15. The problem occurs in both. Here is the stack trace:
|
I am using
pyvsc
in combination withcocotb
andpyhdl-if
. I am using the last two packages heavily and they are great!I started using
pyvsc
for functional coverage and I am getting the following error when running withxcelium/23.09
:After that the stack trace information gets printed.
I found out that solely importing
vsc
viaimport vsc
is causing this issue in my testbench.Then I isolated this by trying the following in a separate file:
which prints out
Aborted (core dumped)
. I am not sure if these two things are related or what is causing this issue.This problem happens after the simulation is completely finished.
This is not so urgent as the simulation can still run normally and finish.
Thanks for maintaining!
The text was updated successfully, but these errors were encountered: