recently I am experiencing a segmentation violation error when trying to compile a Quartus project with the DSE. The single compilation is completed correctly by Quartus, from Analysis&Syntheses to Timing Analysis. However when I launch DSE locally, requiring 10 different compilations, Quartus quits unexpectedly reporting the following error:
*** Fatal Error: Segment Violation at (nil)
0x408f: IPC_COMMAND::parse_output(char const*, unsigned int) + 0xcb (ccl_ipc)
0x4804: IPC_COMMAND::run(std::string const&, std::string const&, bool, unsigned int*, std::string const&, bool) + 0x4ec (ccl_ipc)
0x66efe: CMPM_IPC_CLIENT::thread_proc(void*) + 0x47e (prj_cmpm)
0x602c: thr_final_wrapper + 0xc (ccl_thr)
0x407df: msg_thread_wrapper(void* (*)(void*), void*) + 0x62 (ccl_msg)
0xa559: mem_thread_wrapper(void* (*)(void*), void*) + 0x99 (ccl_mem)
0x8f92: err_thread_wrapper(void* (*)(void*), void*) + 0x27 (ccl_err)
0x63f2: thr_thread_wrapper + 0x15 (ccl_thr)
0x66d2: thr_thread_begin + 0x46 (ccl_thr)
0x76ba: start_thread + 0xca (pthread.so.0)
0x1074dd: clone + 0x6d (c.so.6)
Quartus Prime Version 18.1.0 Build 625 09/12/2018 SJ Standard Edition
OS name: Ubuntu 16.04.6
OS version: 16
Quartus Prime Information
Address bits: 64
Edition: Standard Edition
Has anyone encountered a similar issue?
The things that I have tried so far but unsuccessfully are:
Unfortunately I cannot update Quartus to a newer version.
Dear @KhaiChein_Y_Intel ,
thanks a lot for your answer.
Running DSE using command line works!
Do you know if there is an explanation for this behavior?
I am asking because the same problem may affect other components/processes in Quartus.
Generally, bugs are fixed in the newer version of the software. Since you could not upgrade the design to the latest version, v20.1 to verify if this is fixed in the software, you may use command line as a workaround for v18.1
I’m glad that your question has been addressed, I now transition this thread to community support. If you have a new question, feel free to open a new thread to get the support from Intel experts. Otherwise, the community users will continue to help you on this thread. Thank you