Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 16772
  • 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

Cadence always crash problem

Long Shen

Hi,

Has anyone met with this cadence crashing problem. When I draw some buses in virtuoso, or sometimes descend to a lower cell, my cadence always crashes. I don't know what's the problem.

 

here is the log file

\o INFO (DB-120006): System crashed, you can use dbOpenPanicCellView() to open saved cellViews.
\o virtuoso has encountered a fatal internal application error and will now exit.

Thanks. 

  • Hi Long Shen

    Would you please retry using the latest version of  Virtuoso (IC615-500-12)? If it still crashes, please file a service request with your local Cadence support. Please also include a CDS.log file that contains the crash stack.


    Best regards
    Quek

  • yes I have contact the local support but they need the database from my company which I can't provide because of the company's policy. Just wonder if other users have met the same problem.

    Thanks,

    Long

  • Hi Long Shen

    In that case, would you please upload the CDS.log file which contains the crash stack?

    Thanks
    Quek

  • Hi Quek,

    This is the two log files from Virtuoso.

     

    Thanks,

    Long

    crash.zip

  • Hi Long

    Thanks for the files. From the log file, I can see that you are currently using 64bits IC615-500-10 and it has the following information:

    \o NewPatternRoute:: collecting 10 guides into 1 bundles (0 guides uncollected)
    \o All guides from the set collected and ordered
    \o NewPatternRoute:: collecting 10 guides into 1 bundles (0 guides uncollected)
    \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:_ZN26ctpNewPatternRouteOneGuide9insertViaEP8ctuRouteP9ctuObjectPP11ctuRouteViaR10ctuDBPointPK8ctuLayerSB_b17ctuDirectionIndexjijb.clone.25+45()
    \o virtuoso:_ZN26ctpNewPatternRouteOneGuide11jogOneGuideEP18ctpNormalizedGuide17ctuDirectionIndex+5425()
    \o virtuoso:_ZN26ctpNewPatternRouteOneGuide10crossWiresEP9ctpBundle17ctuDirectionIndexb+282()
    \o virtuoso:_ZN18ctpNewPatternRoute12routeABundleEP9ctpBundleRbbP9ctuDBRectb+2396()
    \o virtuoso:_ZN18ctpNewPatternRoute5routeEP15ctuSelectionSetP9ctuDBRectbb+537()
    \o virtuoso:_ZN22ctdFinishBusRouteUtils14finishBusRouteEP15ctuSelectionSetbbb+10249()
    \o virtuoso:_ZN6vcaP2P11finishRouteEbbbbbbbbbbbbbbi+1663()
    \o virtuoso:_ZN11leWireGroup6finishER6vcaP2Pbb+737()
    \o virtuoso:_ZN17leWireCreationSet6finishER6vcaP2Pbb+100()


    This bug has recently been fixed through CCR1035145 in IC616. Perhaps you can check with your local Cadence support to see if the fix can be backported to IC615.

    Best regards
    Quek

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.