VCS segfaults when compiling code with overridden system calls
See original GitHub issueIn the sim_exit
testcase:
Parsing design file '/home/chiggs/code/github/cocotb/examples/sim_exit/tests/../hdl/close_module.v'
Top Level Modules:
close_module
TimeScale is 1 ps / 1 ps
Starting vcs inline pass...
Got SIGSEGV
An unexpected termination has occurred in /tools/synopsys/vcs/I-2014.03-2/amd64/bin/vcs1 because of a fatal signal
Stmt $info at /home/chiggs/code/github/cocotb/examples/sim_exit/tests/../hdl/close_module.v, 58
Stmt at /home/chiggs/code/github/cocotb/examples/sim_exit/tests/../hdl/close_module.v, 58
Stmt at /home/chiggs/code/github/cocotb/examples/sim_exit/tests/../hdl/close_module.v, 55
Process /home/chiggs/code/github/cocotb/examples/sim_exit/tests/../hdl/close_module.v, 55
During addModuleItems Module close_module declared at /home/chiggs/code/github/cocotb/examples/sim_exit/tests/../hdl/close_module.v, 33
XModule close_module declared at /home/chiggs/code/github/cocotb/examples/sim_exit/tests/../hdl/close_module.v, 33
Hsim mod number=1
Command line: /tools/synopsys/vcs/I-2014.03-2/amd64/bin/vcs1 -Mcc=gcc -Mcplusplus=g++ -Masflags= "-Mcfl= -pipe -fPIC -O -I/tools/synopsys/vcs/I-2014.03-2/include " "-Mldflags= " -Mout=simv -Mamsrun= -Mvcsaceobjs= "-Mobjects= /tools/synopsys/vcs/I-2014.03-2/amd64/lib/libvirsim.so /tools/synopsys/vcs/I-2014.03-2/amd64/lib/liberrorinf.so /tools/synopsys/vcs/I-2014.03-2/amd64/lib/libsnpsmalloc.so " -Msaverestoreobj=/tools/synopsys/vcs/I-2014.03-2/amd64/lib/vcs_save_restore_new.o -Mcrt0= -Mcrtn= -Mcsrc= "-Msyslibs=-ldl -lm -lm " +acc+1 -P pli.tab +define+COCOTB_SIM=1 -Xcbug=0x1 -load libvpi.so -full64 -picarchive +cli+4 +vcsd +itf+/tools/synopsys/vcs/I-2014.03-2/amd64/lib/vcsd.tab +vpi -debug=3 +memcbk +vpi -sverilog +vpi -gen_obj /home/chiggs/code/github/cocotb/examples/sim_exit/tests/../hdl/close_module.v
--- Stack trace follows:
[Thread debugging using libthread_db enabled]
0x00000033ee2ac61e in waitpid () from /lib64/libc.so.6
#0 0x00000033ee2ac61e in waitpid () from /lib64/libc.so.6
#1 0x00000033ee23e609 in do_system () from /lib64/libc.so.6
#2 0x00000000040baac5 in tracker::StackAnnotator::getGdbOutput(char const*, char const*, char const*, char const*) ()
#3 0x00000000040bb08b in tracker::StackAnnotator::dumpStackByGdb(char const*, char const*) ()
#4 0x00000000040bc3b6 in tracker::StackAnnotator::dumpProcessStack(unsigned int, char const*, char const*) ()
#5 0x00000000040b17d8 in ?? ()
#6 0x0000000003d45887 in stackTraceHandler ()
#7 0x0000000003d4420e in SigHandler ()
#8 <signal handler called>
#9 0x00000000030e8600 in SetupMBDaiCapTsk ()
#10 0x0000000002cd0e9a in vcsAddModuleSysTask(Stmt const*, mb*) ()
#11 0x0000000002cdd963 in ?? ()
#12 0x0000000002cdbd80 in ?? ()
#13 0x0000000002cdb6d5 in ?? ()
#14 0x0000000002cde653 in ?? ()
#15 0x0000000002cdfd66 in vcsPutTokenModule(XModule const*) ()
#16 0x0000000002cedebc in vcsAddModuleItems(XModule*) ()
#17 0x0000000002cf3650 in ?? ()
#18 0x0000000002cf405b in vcsCreateModuleStruct(int) ()
#19 0x00000000012320b2 in doRadify_vir2vcsAll ()
#20 0x0000000002fc21dc in ?? ()
#21 0x0000000002fc84be in c_main ()
#22 0x0000000000e68411 in main ()
Completed context dump phase data location 'Stmt'* 'Stmt'* 'Stmt'* 'Process'* 'Module'* 'XModule'*
CPU time: .646 seconds to compile
make[1]: *** [sim_build/simv] Error 1
make[1]: Leaving directory `/home/chiggs/code/github/cocotb/examples/sim_exit/tests'
make: *** [sim] Error 2
Commenting out the system calls ($info
, $fatal
) etc. allow compilation to continue.
Issue Analytics
- State:
- Created 8 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
VCS segfaults when compiling code with overridden system ...
Commenting out the system calls ( $info , $fatal ) etc. allow compilation to continue. The text was updated successfully, but these ...
Read more >Why is a segmentation fault not recoverable? - Stack Overflow
A segfault happens when your program tries to dereference a bad pointer. (See below for a more technical version of ...
Read more >Identify what's causing segmentation faults (segfaults)
A segmentation fault (aka segfault) is a common condition that causes programs to crash; they are often associated with a file named core...
Read more >Segmentation fault - Wikipedia
A segmentation fault occurs when a program attempts to access a memory location that it is not allowed to access, or attempts to...
Read more >VCS® MX/VCS MXi™ User Guide
System Compiler, System Designer, Taurus, TotalRecall, TSUPREM-4, VCSi, ... VCS MX atomically recognizes C/C++ function calls and.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The system task overload were removed in #2133. Can this be closed now?
This test itself does not exist anymore, and its replacement
test_fatal
runs fine in VCS (with #2163 applied).