Re: Fatal error during TimeQuest analyzer

Altera_Forum · ‎12-06-2010

Hi all,

I get the following error when I try running TimeQuest on a particular project:


*** Fatal Error: Segment Violation at (nil)
Module: quartus_sta
Lock in use: 10
Stack Trace:
    0x1b9ce: mem_is_allocated(void*) + 0xe (quartus_sta)
    0x163eb: PDB_SEGMENT_WRITER::write_ptr(PDB_OBJECT_BASE*, PDB_OBJECT_INFO*, bool) + 0x38b (db_pdb)
    0xbbb36: HDB_SOURCE_FILE::operator<<(PDB_SEGMENT_TEMPLATE<PDB_HDB_SEG_BASE>&) + 0x2a6 (db_hdb)
     0xdb0a: PDB_OBJECT_INFO::finish_writing(PDB_SEGMENT_WRITER&) + 0x5a (db_pdb)
    0x1d47a: pdb_write_ptr(PDB_SEGMENT_WRITER&, void (*)(PDB_SEGMENT&, void*&), void*&, int) + 0x7a (db_pdb)
   0x1b4da4: DBM_PDB<HDB_CMP_ACTION_PT_INSTANCE>::write_file(HDB_CMP_ACTION_PT_INSTANCE*, char const*, char const*) + 0x104 (db_hdb)
   0x166c6f: HDB_CMP_ACTION_PT_INSTANCE::write_pdb(FIO_PATH const&, HDB_ACTION_PT_INSTANCE::PDB_FILE_TYPE) + 0x31f (db_hdb)
   0x18fb84: sta_build_tdb_netlist(CDB_CHIP_DB_ENTRY*, STA_EXE_INTERFACE::DB_TYPE&, bool, bool, bool) + 0x144 (tsm_sta)
   0x194289: sta_create_timing_netlist + 0xd79 (tsm_sta)
    0x2fa06: TclEvalObjvInternal + 0x4b6 (tcl8.5)
    0x303c2: TclEvalEx + 0x6a2 (tcl8.5)
    0x30e79: TclEvalObjEx + 0x339 (tcl8.5)
    0x3ab2b: Tcl_EvalObjCmd + 0x3b (tcl8.5)
    0x2fa06: TclEvalObjvInternal + 0x4b6 (tcl8.5)
    0x7207f: TclExecuteByteCode + 0x1baf (tcl8.5)
    0xaf833: TclObjInterpProcCore + 0x123 (tcl8.5)
    0x2fa06: TclEvalObjvInternal + 0x4b6 (tcl8.5)
    0x7207f: TclExecuteByteCode + 0x1baf (tcl8.5)
    0x7938a: TclCompEvalObj + 0x9a (tcl8.5)
    0x30c8f: TclEvalObjEx + 0x14f (tcl8.5)
    0x40431: Tcl_IfObjCmd + 0x221 (tcl8.5)
    0x2fa06: TclEvalObjvInternal + 0x4b6 (tcl8.5)
    0x7207f: TclExecuteByteCode + 0x1baf (tcl8.5)
    0xaf833: TclObjInterpProcCore + 0x123 (tcl8.5)
    0x2fa06: TclEvalObjvInternal + 0x4b6 (tcl8.5)
    0x303c2: TclEvalEx + 0x6a2 (tcl8.5)
    0x947b9: Tcl_FSEvalFileEx + 0x209 (tcl8.5)
    0x9491e: Tcl_EvalFile + 0x2e (tcl8.5)
    0x10f93: qexe_evaluate_tcl_script(char const*) + 0x693 (comp_qexe)
    0x1174c: qexe_do_tcl(QEXE_FRAMEWORK*, char const*, char const*, _Dinkum_std::list<_Dinkum_std::basic_string<char, _Dinkum_std::char_traits<char>, MEM_STL_ALLOCATOR<char> >, MEM_STL_ALLOCATOR<_Dinkum_std::basic_string<char, _Dinkum_std::char_traits<char>, MEM_STL_ALLOCATOR<char> > > > const&, bool, bool) + 0x5a8 (comp_qexe)
    0x12402: qexe_run_tcl_option(QEXE_FRAMEWORK*, char const*, _Dinkum_std::list<_Dinkum_std::basic_string<char, _Dinkum_std::char_traits<char>, MEM_STL_ALLOCATOR<char> >, MEM_STL_ALLOCATOR<_Dinkum_std::basic_string<char, _Dinkum_std::char_traits<char>, MEM_STL_ALLOCATOR<char> > > >*, bool) + 0x7c8 (comp_qexe)
    0x59373: qcu_run_tcl_option(QCU_FRAMEWORK*, char const*, _Dinkum_std::list<_Dinkum_std::basic_string<char, _Dinkum_std::char_traits<char>, MEM_STL_ALLOCATOR<char> >, MEM_STL_ALLOCATOR<_Dinkum_std::basic_string<char, _Dinkum_std::char_traits<char>, MEM_STL_ALLOCATOR<char> > > >*, bool) + 0x931 (comp_qcu)
    0x1aee5: qsta_tcl_process_sta_mode_option(ACF_VARIABLE_TYPE_ENUM, char const*) + 0x55 (quartus_sta)
    0x1a45f: qexe_standard_main(QEXE_FRAMEWORK*, QEXE_OPTION_DEFINITION const**, int, char const**) + 0x39f (comp_qexe)
    0x1adc0: qsta_main(int, char const**) + 0x90 (quartus_sta)
    0x2c980: msg_main_thread(void*) + 0x10 (ccl_msg)
     0x6e7e: thr_final_wrapper + 0xc (ccl_thr)
    0x2ded3: msg_thread_wrapper(void* (*)(void*), void*) + 0x65 (ccl_msg)
    0x36a78: mem_thread_wrapper(void* (*)(void*), void*) + 0xc8 (quartus_sta)
     0x94a1: err_thread_wrapper(void* (*)(void*), void*) + 0x25 (ccl_err)
     0x6e98: thr_thread_wrapper + 0x15 (ccl_thr)
    0x4045b: msg_exe_main(int, char const**, int (*)(int, char const**)) + 0x77 (ccl_msg)
    0x1c3fb: __libc_start_main + 0xdb (c.so.6)
End-trace

I've tried restarting and running the entire build all over again, but I didn't have any luck. I noticed that part of the error said "lock in use" ... could that be a clue to something?

Altera support hasn't been much help on this...

Altera_Forum · ‎12-06-2010

When you ran the build over, did you delete the DB and incremental DB directories? Sometimes a corrupted DB file will cause issues like this..

Pete