impore function GotScoreboards – Fatal: (SIGSEGV) Bad handle or reference.
Why OSVVM™? › Forums › OSVVM › impore function GotScoreboards – Fatal: (SIGSEGV) Bad handle or reference.
Tagged: osvvm
- This topic has 2 replies, 2 voices, and was last updated 1 year ago by
Cahit.
-
AuthorPosts
-
September 9, 2024 at 11:15 #2567
Cahit
MemberHi,
I am building a unit test for a large function that we use, but during report generation (EndOfTestReports) I get the following error.
# ** Fatal: (SIGSEGV) Bad handle or reference. # Time: 3 ns Iteration: 2 Process: /***_tb/test_ctrl_i/control_p File: /***/OsvvmLibraries/osvvm/ScoreboardGenericPkg.vhd # Fatal error in Subprogram GotScoreboards at /***/OsvvmLibraries/osvvm/ScoreboardGenericPkg.vhd line 3388 # # HDL call sequence: # Stopped at /***/OsvvmLibraries/osvvm/ScoreboardGenericPkg.vhd 3388 Subprogram GotScoreboards # called from /***/OsvvmLibraries/osvvm/ReportPkg.vhd 132 Subprogram EndOfTestReports # called from /***/OsvvmLibraries/osvvm/ReportPkg.vhd 182 Subprogram EndOfTestReports # called from ../i***_tb.vhd 48 Process control_p
The function that causes the error is the “GotScoreboards” function in ScoreboardGeneriPkg.vhd.
My testbench is fairly a simple testbench, where I call the “function under test” with various input parameters and affirm the output values with the reference values, that I generate with an external model (C#). The testbench is written in combinatorial fashion (no clock, no reset, etc.) with a wait 1ps statement after each iteration. Before the report generation there is no error and my testcase comes to an end.
%% 3 ns DONE PASSED ***_tc Passed: 2999 Affirmations Checked: 2999
The testbench doesn’t have any scoreboards, so the “GotScoreboards” function should return false during report generation, but instead I get the above error message.
So, everything is pretty much a standard OSVVM testcase. The only part, that is out of standard is, that I don’t compile the source codes using OSVVM “analyze” API, instead I map a pre-compiled library using “LinkLibrary” API. I don’t see, how this should make a difference, but I wanted to mention it to complete the picture.
Tool List:
OSVVM Script Version: 2024.05b
Simulator Version: ModelSim-2016.04Has anyone experience a similar error? Could anyone direct me to the source of the error?
Many thanks.
September 9, 2024 at 13:10 #2568Jim Lewis
MemberHi Cahit,
That is a bug in ModelSim 2016.04.In addition to that bug, you may run into scripting issues as the version of TCL is with 2016 is too old.
You will need a newer simulator version. Keep in mind that simulator is 8 years old at this point. They have fixed many bugs since then.
Best Regards,
JimSeptember 10, 2024 at 08:51 #2569Cahit
MemberHi Jim,
That’s good to know. Thanks!I did have issues running the osvvm demo as well, but luckyly my testbench is working – except the reporting part. We will be switching to a newer ModelSim version soon. I will try it out after the change.
Many thanks!
Cahit -
AuthorPosts
- You must be logged in to reply to this topic.