Stats

  • Locked Locked
  • Replies 10
  • Subscribers 125
  • Views 20713
  • 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

Virtuoso continues to crash

Miguel V

Hi,

I have a colleague who keeps having issues with virtuoso unexpectedly crashing whenever she tries to open a layout in either read or edit mode.  Some cells are fine, but there are some that crash every single time, even tried to jump to a different server or create a new workarea.  I've tried to have her copy the layout in question but the crashing still happens.  Also, it doesn't matter what version of Virtuoso we use, the result is always the same.  

Parents

  • You should contact customer support, and provide the crash log and CDS.log from the session where the crash occurred (ideally produce a few if they are reproducible on different designs). The signature of the crash can often help us identify if it's a known issue that's been resolved in a newer version.You didn't mention which versions are being used or whether these are recent or not.

    The other thing that is worth doing is (from the UNIX prompt) "oaScan -lib theLibName" to see if there is any database corruption in the design that needs fixing.

    Regards,

    Andrew.

Reply

  • You should contact customer support, and provide the crash log and CDS.log from the session where the crash occurred (ideally produce a few if they are reproducible on different designs). The signature of the crash can often help us identify if it's a known issue that's been resolved in a newer version.You didn't mention which versions are being used or whether these are recent or not.

    The other thing that is worth doing is (from the UNIX prompt) "oaScan -lib theLibName" to see if there is any database corruption in the design that needs fixing.

    Regards,

    Andrew.

Children
  • in reply to Andrew Beckett

    Hi Andrew, thanks for the command.  I tried this running IC version 6.1.6, 6.1.7 and 6.1.8  Just before the crash we get a SIGSEV error and cadence closes, then we get a pop-up asking us to view the report.  How do I repair any corruption?  I ran the scan and I get numerous ERROR SCAN-211 or 93 errors on the cells that are giving us problems:

    ERROR SCAN-211  Repair needed for inconsistent appData reference on a inst

    ERROR SCAN-211  Repair needed for inconsistent appData reference on a shape

    ERROR SCAN-211  Repair needed for inconsistent appData reference on a via

    cellview <LIB>/<CELLNAME>/layout 'maskLayout' 

    -data model 0 saved by an app compiled against 22.60.007 running 22.60.007

    -platform linux_rhel60_64 gcc_6.3.0

  • in reply to Miguel V

    If you run oaScan with the -repair option it will fix these...

    This is assuming that it's the info found during the oaScan which is causing the crash. If it still crashes after the repair, you absolutely should contact customer support (I'd also suggest using IC618 to open the repaired data, in case it's an older buggy version which is introducing the inconsistent appData).

    Regards,

    Andrew.

  • in reply to Andrew Beckett

    Hi Andrew,

    Thank you, that worked like a charm.  Issues were repaired and now the cells open up without crashing, thanks.

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.