Forum Discussion

Nick_kb's avatar
Nick_kb
Icon for New Contributor rankNew Contributor
1 month ago
Solved

Error:invalid command name "Quartus"

 

I am running Quartus GUI on a Linux server remotely through an SSH session.

One of the below two issues happens 50% of the time after starting compilation

  1. Quartus hangs during a stage of compilation showing as if it is working (timer is increasing) but nothing is happening and no substantial CPU usages is observed. Trying to stop compilation fails and attempting to close the project fails giving the below message:
  2. Quartus fails compilation and gives below tcl message

o   Error:invalid command name "Quartus"

o   Error:    while executing

o   Error:"unknown_original Quartus 0x202ca: (ld-linux-x86-64)"

o   Error:    ("eval" body line 1)

o   Error:    invoked from within

o   Error:"eval unknown_original $cmd $args"

o   Error:    (procedure "::unknown" line 7)

o   Error:    invoked from within

o   Error:"Quartus          0x202ca: (ld-linux-x86-64)"

o   Error:    invoked from within

o   Error:"flng::run_flow_command -flow "compile" -end "dni_tlg" -resume"

 

After closing or killing Quartus, opening it again fails and the terminal shows below message:

 

Error (22912): Unhandled exception:

Fatal Error: Assertion failed tools/cpp/ddm/ddm_assessor.cpp:53: DDM_T::verify_token(token) : Cannot identify the client

 from function assertion_error in tools/cpp/ddm_report/ddm_report_msg.cpp@465

 

*** Fatal Error: Program termination requested

***

*** Below is the stack trace at the time the error occurred.

*** The lines beginning "Err Handler" represent frames relating

*** to generating this report.

*** The point at which the error occurred is somewhere after these lines.

*** There may be a few frames representing standard/library code

*** before the Quartus frames begin.

*** The search for the error should begin with the Quartus frames.

 

*** Unwinder: libunwind

*** Stack depth: 15

 

  Quartus          0x23dd9: err_terminator() + 0x1bc (ccl_err)

  Quartus          0xb036a: __cxxabiv1::__terminate(void (*)()) + 0xa (stdc++)

  Quartus          0xb03d5: (stdc++)

  Quartus          0xb0628: (stdc++)

  Quartus          0x1684d: void ddm_throw<DDM_RUNTIME_ERROR>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0x26d (ddm_report)

  Quartus          0x13f3e: DDM_REPORT::DDM_ASSERTION_HANDLER::assertion_error(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) const + 0xde (ddm_report)

  Quartus          0x129e2: DDM_REPORT::ASSERTION_HANDLER::error(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) + 0x72 (ddm_report)

  Quartus          0x13df4: DDM_REPORT::detail::assert_at_line(char const*, char const*, int, char const*, ...) + 0x1b4 (ddm_report)

  Quartus         0x1debb0: ddm_set_lassessor(DDM_T_ASSESSOR*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0x60 (ddm)

  Quartus          0xeedc7: DMS_MANAGER::DMS_MANAGER() + 0x21f (dni_dms)

  Quartus          0xeef48: DMS_MANAGER::get() + 0x7a (dni_dms)

  Quartus          0xf163b: _GLOBAL__sub_I_dms_manager.cpp + 0x58 (dni_dms)

  Quartus           0x647e: (ld-linux-x86-64)

  Quartus           0x6568: (ld-linux-x86-64)

  Quartus          0x202ca: (ld-linux-x86-64)

 

Checking running processes shows no Quartus related processes at this stage

How can we solve this issue please?

4 Replies

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

    Yes, you may see that forum pin the critical issue in https://community.altera.com/discussions/quartus-prime/critical-notice-ddm-error--crash-issue-in-quartus%C2%AE-prime-pro-v23-3%E2%80%93v25-3-1-%E2%80%94-act/349761

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

      No thanks. the problem is solved now