Forum Discussion

StasM's avatar
StasM
Icon for New Contributor rankNew Contributor
3 years ago

Quartus Prime v. 21.1.1: Fatal Error: Segment Violation

Hi,

I am using Quartus Prime ver. 21.1.1 Build 850 06/23/2022 SJ Lite Edition for development on a Cyclone V board (DE10-Nano). I am using the Linux version of the software.

When compiling a project from the Quartus Prime GUI, the program sometimes crashes with a segfault. I am not 100% sure, but I think this mostly happens when the simulation netlist generation is enabled in the settings.

Here is the complete crash log:

Problem Details
Error:
*** Fatal Error: Segment Violation at 0x18
Module: quartus
Stack Trace:
    0x28f2b: gen_stricmp(char const*, char const*) + 0x1c (ccl_gen)
    0x34b3c: TMWQ_TREE::check_for_valid_design_assistant(bool, int, TMWQ_ITEM*) + 0xa4 (resr_tmwq)
    0x460a0: TMWQ_TREE::populate_tree_with_percentage(BAT_STATUS_OBJECT const&, std::list<BAT_STATUS_BOX*, std::allocator<BAT_STATUS_BOX*> > const&, int) + 0x2ae (resr_tmwq)
    0x4633d: TMWQ_TREE::populate_tree_with_percentage(BAT_STATUS_OBJECT const&, std::list<BAT_STATUS_BOX*, std::allocator<BAT_STATUS_BOX*> > const&, int) + 0x54b (resr_tmwq)
    0x465fb: TMWQ_TREE::on_status_updated(BAT_STATUS_OBJECT const&) + 0xef (resr_tmwq)
    0x4a3be: TMWQ_TREE::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 0x1e0 (resr_tmwq)
   0x2fb7a3: void doActivate<false>(QObject*, int, void**) + 0x263 (Qt5Core.so.5)
    0xc9909: QUI_STATUS_MONITOR::status_updated(BAT_STATUS_OBJECT const&) + 0x35 (sys_qui)
    0xc9c74: QUI_STATUS_MONITOR::emit_status_updated_signal(bool) + 0x12 (sys_qui)
    0xc9c8e: QUI_STATUS_MONITOR::emit_status_updated() + 0x14 (sys_qui)
    0xc9cb7: QUI_STATUS_MONITOR::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 0x27 (sys_qui)
   0x2fb7a3: void doActivate<false>(QObject*, int, void**) + 0x263 (Qt5Core.so.5)
   0x300607: QTimer::timeout(QTimer::QPrivateSignal) + 0x37 (Qt5Core.so.5)
   0x300908: QTimer::timerEvent(QTimerEvent*) + 0x28 (Qt5Core.so.5)
   0x2f28f3: QObject::event(QEvent*) + 0xa3 (Qt5Core.so.5)
   0x15befc: QApplicationPrivate::notify_helper(QObject*, QEvent*) + 0x9c (Qt5Widgets.so.5)
   0x162f60: QApplication::notify(QObject*, QEvent*) + 0x220 (Qt5Widgets.so.5)
   0x2c07b0: QCoreApplication::notifyInternal2(QObject*, QEvent*) + 0x110 (Qt5Core.so.5)
   0x31f289: QTimerInfoList::activateTimers() + 0x489 (Qt5Core.so.5)
   0x31d59f: QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 0x4bf (Qt5Core.so.5)
    0x6519e: QXcbUnixEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 0xe (Qt5XcbQpa.so.5)
    0x60d09: qui_call_app_process_event + 0x39 (sys_qui)
     0x4d00: thr_qt_process_events + 0x52 (ccl_thr)
    0x18aa2: flow_process_events() + 0x9 (sys_flow)
    0x19b74: flow_call_cmd(FLOW_FACADE*, char const*) + 0x1f8 (sys_flow)
    0x22c91: flow_generic_call(FLOW_FACADE*, char const*, char const*, bool) + 0x16d (sys_flow)
    0x25705: flow_do_generic_flow(FLOW_FACADE*, FLOW_NAME_CMD_PAIR*, HDB_NAMESPACE::SMART_ACTION) + 0x1bf (sys_flow)
    0x3674f: flow_full_compile_or_simulate(FLOW_FACADE*, FLOW_INFO, bool, std::vector<std::string, std::allocator<std::string> >*) + 0x1db0 (sys_flow)
    0x370ca: flow_compile(FLOW_FACADE*, FLOW_INFO) + 0x4e (sys_flow)
    0x283e0: flow_execute_custom + 0x80a (sys_flow)
    0x28f30: flow_execute + 0x142 (sys_flow)
    0x63f63: QUI_APP::on_start_flow(int, QString) + 0x37f (sys_qui)
    0xcbfa2: QUI_APP::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 0x13a (sys_qui)
   0x2f293b: QObject::event(QEvent*) + 0xeb (Qt5Core.so.5)
   0x1441c1: QGuiApplication::event(QEvent*) + 0x41 (Qt5Gui.so.5)
   0x16152c: QApplication::event(QEvent*) + 0x5c (Qt5Widgets.so.5)
   0x15befc: QApplicationPrivate::notify_helper(QObject*, QEvent*) + 0x9c (Qt5Widgets.so.5)
   0x162f60: QApplication::notify(QObject*, QEvent*) + 0x220 (Qt5Widgets.so.5)
   0x2c07b0: QCoreApplication::notifyInternal2(QObject*, QEvent*) + 0x110 (Qt5Core.so.5)
   0x2c39e2: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 0x232 (Qt5Core.so.5)
   0x31d134: QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 0x54 (Qt5Core.so.5)
    0x6519e: QXcbUnixEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 0xe (Qt5XcbQpa.so.5)
   0x2bf01a: QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 0x11a (Qt5Core.so.5)
   0x2c87d7: QCoreApplication::exec() + 0x97 (Qt5Core.so.5)
     0x1f2b: qgq_main(int, char const**) + 0x7b (quartus)
    0x3ee30: msg_main_thread(void*) + 0x10 (ccl_msg)
     0x5acc: thr_final_wrapper + 0xc (ccl_thr)
    0x3eeef: msg_thread_wrapper(void* (*)(void*), void*) + 0x62 (ccl_msg)
     0x9f9c: mem_thread_wrapper(void* (*)(void*), void*) + 0x5c (ccl_mem)
     0x91d9: err_thread_wrapper(void* (*)(void*), void*) + 0x27 (ccl_err)
     0x5b0f: thr_thread_wrapper + 0x15 (ccl_thr)
    0x40ea1: msg_exe_main(int, char const**, int (*)(int, char const**)) + 0xb2 (ccl_msg)
     0x2011: main + 0x26 (quartus)
    0x23d0a: __libc_start_main + 0xea (c.so.6)
 
 
End-trace


Executable: quartus
Comment:
None

System Information
Platform: linux64
OS name: Debian GNU/Linux
OS version: 11

Quartus Prime Information
Address bits: 64
Version: 21.1.1
Build: 850
Edition: Lite Edition

7 Replies

  • StasM's avatar
    StasM
    Icon for New Contributor rankNew Contributor

    Hi,

    I have to correct myself: the segfaults happen not when the simulation netlist generation is enabled, but when the option "Run Design Assistant during compilation" is enabled in the options.

    Hope this can be easily fixed.

    BR,

    StasM

  • SyafieqS's avatar
    SyafieqS
    Icon for Super Contributor rankSuper Contributor

    Hi Stanislav,


    Sometime means intermittently when the option "Run Design Assistant during compilation" is enabled in the options?

    May I know if it is possible for you to attach the archived design for me to replicate, might be design dependent.

    If yes, seem to me like a valid bug


    • StasM's avatar
      StasM
      Icon for New Contributor rankNew Contributor

      Hi,

      Yes, here "sometimes" means occasionally, from time to time. By the way, recently I got another segfault even when the option "Run Design Assistant during compilation" was disabled in settings. So, the problem can be more complex. Unfortunately, I cannot send you the project files because it is a confidential information. I can send you crash reports. Here is the last crash report:

      Problem Details
      Error:

      *** Fatal Error: Segment Violation at 0xffffffffffffffe8
      Module: quartus
      Stack Trace:
      0x42d5e: TMWQ_TREE::start_next_task(bool) + 0x102 (resr_tmwq)
      0x438ea: TMWQ_TREE::on_start_next_task() + 0xe (resr_tmwq)
      0x4a3ca: TMWQ_TREE::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 0x1ec (resr_tmwq)
      0x2fb7a3: void doActivate<false>(QObject*, int, void**) + 0x263 (Qt5Core.so.5)
      0x30b80: TMWQ_TREE::start_next_task_signal() + 0x1a (resr_tmwq)
      0x42c45: TMWQ_TREE::compile_finished() + 0x11 (resr_tmwq)
      0x4a275: TMWQ_TREE::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 0x97 (resr_tmwq)
      0x2fb7a3: void doActivate<false>(QObject*, int, void**) + 0x263 (Qt5Core.so.5)
      0x22cce: TMWQ_WIDGET::post_flow_finish() + 0x1a (resr_tmwq)
      0x23359: TMWQ_WIDGET::ntfq_msg_post_notify_flow_finish(unsigned long, bool) + 0x2f (resr_tmwq)
      0x2315a: TMWQ_NTFQ::ntfq_msg_post_notify_flow_finish(unsigned long, bool) + 0x14 (resr_tmwq)
      0x2902: NTFQ_NOTIFY_TARGET::dispatch_notify_msg(NTFQ_NOTIFY_MAP const*, unsigned int, unsigned long, bool) + 0x56 (ccl_ntfq)
      0x2987: NTFQ_NOTIFY_TARGET::on_ntfq_notify(unsigned int, unsigned long, bool) + 0x3d (ccl_ntfq)
      0x2e08: NTFQ_NOTIFY_MGR::broadcast_notify(unsigned int, unsigned long) + 0xca (ccl_ntfq)
      0x2b7b: ntfq_broadcast_notify(unsigned int, unsigned long) + 0x26 (ccl_ntfq)
      0x1a240: flow_reset(FLOW_INFO*) + 0x73 (sys_flow)
      0x28b70: flow_execute_custom + 0xf9a (sys_flow)
      0x43570: TMWQ_TREE::start_next_task(bool) + 0x914 (resr_tmwq)
      0x46992: TMWQ_TREE::start(TMWQ_ITEM*) + 0x17a (resr_tmwq)
      0x46c28: TMWQ_TREE::on_start(QModelIndex const&) + 0x272 (resr_tmwq)
      0x46f2c: TMWQ_TREE::on_double_click_text(QModelIndex const&) + 0x1f8 (resr_tmwq)
      0x4a3ae: TMWQ_TREE::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 0x1d0 (resr_tmwq)
      0x2fb7a3: void doActivate<false>(QObject*, int, void**) + 0x263 (Qt5Core.so.5)
      0x3b1dd5: QAbstractItemView::doubleClicked(QModelIndex const&) + 0x35 (Qt5Widgets.so.5)
      0x428f66: QTreeView::mouseDoubleClickEvent(QMouseEvent*) + 0x1d6 (Qt5Widgets.so.5)
      0x189e72: AFCQ_TREE_VIEW::mouseDoubleClickEvent(QMouseEvent*) + 0x24 (gcl_afcq)
      0x19b647: QWidget::event(QEvent*) + 0xa87 (Qt5Widgets.so.5)
      0x2456ce: QFrame::event(QEvent*) + 0x1e (Qt5Widgets.so.5)
      0x3beb43: QAbstractItemView::viewportEvent(QEvent*) + 0x1b3 (Qt5Widgets.so.5)
      0x42accc: QTreeView::viewportEvent(QEvent*) + 0x3c (Qt5Widgets.so.5)
      0x18a14d: AFCQ_TREE_VIEW::viewportEvent(QEvent*) + 0x2cb (gcl_afcq)
      0x2c0530: QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 0xa0 (Qt5Core.so.5)
      0x15bed2: QApplicationPrivate::notify_helper(QObject*, QEvent*) + 0x72 (Qt5Widgets.so.5)
      0x163a30: QApplication::notify(QObject*, QEvent*) + 0xcf0 (Qt5Widgets.so.5)
      0x2c07b0: QCoreApplication::notifyInternal2(QObject*, QEvent*) + 0x110 (Qt5Core.so.5)
      0x1624e2: QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) + 0x212 (Qt5Widgets.so.5)
      0x1b4e8e: QWidgetWindow::handleMouseEvent(QMouseEvent*) + 0x6fe (Qt5Widgets.so.5)
      0x1b7e23: QWidgetWindow::event(QEvent*) + 0x2d3 (Qt5Widgets.so.5)
      0x15befc: QApplicationPrivate::notify_helper(QObject*, QEvent*) + 0x9c (Qt5Widgets.so.5)
      0x162f60: QApplication::notify(QObject*, QEvent*) + 0x220 (Qt5Widgets.so.5)
      0x2c07b0: QCoreApplication::notifyInternal2(QObject*, QEvent*) + 0x110 (Qt5Core.so.5)
      0x1484ad: QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 0xbbd (Qt5Gui.so.5)
      0x1494b5: QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 0x135 (Qt5Gui.so.5)
      0x1238eb: QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 0xbb (Qt5Gui.so.5)
      0x651b3: QXcbUnixEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 0x23 (Qt5XcbQpa.so.5)
      0x2bf01a: QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 0x11a (Qt5Core.so.5)
      0x2c87d7: QCoreApplication::exec() + 0x97 (Qt5Core.so.5)
      0x1f2b: qgq_main(int, char const**) + 0x7b (quartus)
      0x3ee30: msg_main_thread(void*) + 0x10 (ccl_msg)
      0x5acc: thr_final_wrapper + 0xc (ccl_thr)
      0x3eeef: msg_thread_wrapper(void* (*)(void*), void*) + 0x62 (ccl_msg)
      0x9f9c: mem_thread_wrapper(void* (*)(void*), void*) + 0x5c (ccl_mem)
      0x91d9: err_thread_wrapper(void* (*)(void*), void*) + 0x27 (ccl_err)
      0x5b0f: thr_thread_wrapper + 0x15 (ccl_thr)
      0x40ea1: msg_exe_main(int, char const**, int (*)(int, char const**)) + 0xb2 (ccl_msg)
      0x2011: main + 0x26 (quartus)
      0x23d0a: __libc_start_main + 0xea (c.so.6)


      End-trace


      Executable: quartus
      Comment:
      None

      System Information
      Platform: linux64
      OS name: Debian GNU/Linux
      OS version: 11

      Quartus Prime Information
      Address bits: 64
      Version: 21.1.1
      Build: 850
      Edition: Lite Edition

  • SyafieqS's avatar
    SyafieqS
    Icon for Super Contributor rankSuper Contributor

    Hello Stanislav,


    Without a small design, its hard to debug. Since there is confidential information, you can still send me your compilation database without sending my source design files. May follow below kdb.

    This will expedite the process.




  • SyafieqS's avatar
    SyafieqS
    Icon for Super Contributor rankSuper Contributor

    Hello Stanislav,


    May I know if there is any update from previous reply?


  • SyafieqS's avatar
    SyafieqS
    Icon for Super Contributor rankSuper Contributor

    As we do not receive any response from you on the previous question/reply/answer that we have provided. Please login to ‘https://supporttickets.intel.com’, view details of the desire request, and post a feed/response within the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support. The community users will be able to help you on your follow-up questions.


    p/s: If any answer from community or Intel support are helpful, please feel free to mark as solution, give Kudos and rate 10/10 survey