ibex icon indicating copy to clipboard operation
ibex copied to clipboard

Generate coverage report error

Open fengfenglong123 opened this issue 8 months ago • 1 comments

Hi team, I use the VCS-2023.12-SP2 tool to run/git/ibex/dv/uvm/core_ibex/Makefile scripts, compile and simulate core_ibex, and also want to view the coverage report of the generated results. However, I keep getting an error when generating the coverage report. How can I solve this problem? The error content is a segment fault. I have tried many methods such as patch fixes like 1patch, but I am unable to generate the coverage report. I hope you can explain and reply. Thank you! Specific error content: Command line: /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/bin/urg1 -full64 -dir shared_cov/test.vdb -report report  --- Stack trace follows:  Error-[URG-LTFF] Load test failed A fatal error occurred while loading the test 'shared_cov/test/test_riscv_pmp_full_random_test_250877', and URG has to exit. The test directory may have been corrupted. Please try regenerating it.

Command line: /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/bin/urg1 -full64 -dir shared_cov/test.vdb -report report [New LWP 6195] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x00000e512ed107e3 in wait4 () from /lib/x86_64-linux-gnu/libc.so.6  Thread 2 (Thread 0xe51287ff6c0 (LWP 6195) "urg1"): #0 0x00000e5130c7d613 in SNPSle_d35ca1ff70d465c2b9b1a72eee90a50630165806651fae96c1bbda5b5d02066c () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/liberrorinf.so #1 0x0000000000634d05 in coverageLoadFailureHandler () #2 0x0000000000e10e1f in ?? () #3 #4 0x00000e51315bcac2 in mem_malloc () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/libsnpsmalloc.so #5 0x00000e51315a04b8 in snpsCheckMallocFunc () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/libsnpsmalloc.so #6 0x00000e512fe20716 in IHpHzgDXd2iK6NZ () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/libucapi.so #7 0x00000e512fe2095e in A7GQifRdzmAtklv () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/libucapi.so #8 0x00000e512fe1f9f6 in WhJQMznS31QJIUI () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/libucapi.so #9 0x00000e512fe1a838 in s8aDH8VrpXrj0yH () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/libucapi.so #10 0x00000e512fe1acf2 in e7chhlyhnRlTIYG () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/libucapi.so #11 0x00000e512fe1b705 in Vl6KyK9mfJFPvEn () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/libucapi.so #12 0x00000e512fe0724b in etYVjBfc5eNb73N () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/libucapi.so #13 0x00000e512fdfca05 in sWX2zp () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/libucapi.so #14 0x00000e512ec9caa4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #15 0x00000e512ed29c3c in ?? () from /lib/x86_64-linux-gnu/libc.so.6  Thread 1 (Thread 0xe5131561d00 (LWP 6095) "urg1"): #0 0x00000e512ed107e3 in wait4 () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00000e512ec585bb in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00000e5130c83940 in SNPSle_10ee25eff68cd8461c9146fa1d0b35e87067f3c8015b313e639d2928478c79b3f673f99203bcf8be64600612100082236bffb2007f1e0ef9 () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/liberrorinf.so #3 0x00000e5130c83f50 in SNPSle_10ee25eff68cd8461c9146fa1d0b35e87067f3c8015b313e81c34e9ac4c8988ef4a6e067b3aa9271e9f15440f9e8f69e71727f1bc8d6ddca () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/liberrorinf.so #4 0x00000e5130c8558a in SNPSle_10ee25eff68cd8461c9146fa1d0b35e87067f3c8015b313efba706aab251478fa49e66610e453774633a6c152e7ef778f93045171fb3645d () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/liberrorinf.so #5 0x00000e5130c7d633 in SNPSle_d35ca1ff70d465c2b9b1a72eee90a50630165806651fae96c1bbda5b5d02066c () from /home/liu/synopsys_apps/vcs/V-2023.12-SP2/linux64/lib/liberrorinf.so 

fengfenglong123 avatar May 27 '25 14:05 fengfenglong123

Is this an issue you should be reporting to your tool provider?

marnovandermaas avatar May 29 '25 14:05 marnovandermaas