Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 13973
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Fatal Application Error in ASSURA av_extracted

Bayes
Hi,

I am using 6.1.5 environment and I'm running ASSURA to perform DRC and LVS and it is all right.

Unfortunatelly, then, when I try to run Assura Parasitic Extraction, to generate an extracted view (av_extracted), I have a serious problem since I have the crash of CADENCE and I don't understand where is the problem.

In attachment there are the window that appears when there is the system crash and the related generated log files.
What's happening? What can I do to solve this error/problem?

Thanks a lot in advance for your help,

Andrea.
CrashReport.zip
Parents
  • Quek

    Hi Andrea

    It looks like you were running rcx 41 on IC615-500.6 when Virtuoso crashed. This seems to be the same form resize bug which has already been fixed in IC615-500-14. I think you should not see the crash if you use any version higher than IC615-500-14 (e.g. IC616).

    Usually the first few lines of the crash stack is the most important as it helps in identifying the crash signature.

    \o cmd  is /ic_tools/cds/ASSURA.4.1.OA.615/tools/assura/bin/assura /home/cadence/ASSURA_LVS/r_to_t3_core/rcx.r_to_t3_core.rsf -cdslib /home/cadence/cds.lib
    \o Starting the ipc:10 Run: IPC Id 5708: pid "Assura RCX".
    \e *Error* The Assura RCX run "r_to_t3_core" failed!
    \e     The log File is at: /home/cadence/ASSURA_LVS/r_to_t3_core/rcx.r_to_t3_core.log
    \o INFO (DB-170018): (dbPanic) dumping stack
    \o virtuoso:dbPanic+216()
    \o libvirtuos_sh.so:voDoAbortFuncs+37()
    \o libvirtuos_sh.so:voSigAbort+181()
    \o :__kernel_sigreturn+0()
    \o virtuoso:_ZN7HiQForm6resizeEii+89()
    \o virtuoso:_ZN7HiQForm10setExtentsEb+1011()
    \o virtuoso:_Z18hiiInstantiateFormRK13FormStructPtrPN2hi14FieldContainerE+1387()
    \o virtuoso:hifDisplayForm+688()
    \o libil_sh.so:iliVcodeEval2+10526()
    \o libil_sh.so:ilxSkillEval2+220()


    Best regards
    Quek

Reply
  • Quek

    Hi Andrea

    It looks like you were running rcx 41 on IC615-500.6 when Virtuoso crashed. This seems to be the same form resize bug which has already been fixed in IC615-500-14. I think you should not see the crash if you use any version higher than IC615-500-14 (e.g. IC616).

    Usually the first few lines of the crash stack is the most important as it helps in identifying the crash signature.

    \o cmd  is /ic_tools/cds/ASSURA.4.1.OA.615/tools/assura/bin/assura /home/cadence/ASSURA_LVS/r_to_t3_core/rcx.r_to_t3_core.rsf -cdslib /home/cadence/cds.lib
    \o Starting the ipc:10 Run: IPC Id 5708: pid "Assura RCX".
    \e *Error* The Assura RCX run "r_to_t3_core" failed!
    \e     The log File is at: /home/cadence/ASSURA_LVS/r_to_t3_core/rcx.r_to_t3_core.log
    \o INFO (DB-170018): (dbPanic) dumping stack
    \o virtuoso:dbPanic+216()
    \o libvirtuos_sh.so:voDoAbortFuncs+37()
    \o libvirtuos_sh.so:voSigAbort+181()
    \o :__kernel_sigreturn+0()
    \o virtuoso:_ZN7HiQForm6resizeEii+89()
    \o virtuoso:_ZN7HiQForm10setExtentsEb+1011()
    \o virtuoso:_Z18hiiInstantiateFormRK13FormStructPtrPN2hi14FieldContainerE+1387()
    \o virtuoso:hifDisplayForm+688()
    \o libil_sh.so:iliVcodeEval2+10526()
    \o libil_sh.so:ilxSkillEval2+220()


    Best regards
    Quek

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.