• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Virtuoso crashing

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 14232
  • 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 crashing

sray
sray over 6 years ago

Hello

Cadence Virtuoso has been crashing on me multiple times per day.  Two example crash reports are attached. My version information is: "@(#)$CDS: virtuoso version 6.1.7-64b 12/01/2016 05:43 (sjfhw306) $".

crashReport_A.txt

crashReport_B.txt

An empirical observation is that the moment of crashing is always when interacting with Schematic Editor L, for example when closing a tab or editing parameters of a component. A colleague of mine is running Virtuoso on the same machine (to which we're both ssh'ed into and -X forwarding), and I verified that not only is my version identical to his but other files--.cdsenv, .cdsinit, .tcshrc, setup.csh--are too.

Any help would be appreciated!

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    You should contact customer support - that is the proper process for dealing with these things. The crash logs are a little odd - there isn't really much of a stack trace in the logs.

    Please provide customer support with both the crash log and the CDS.log when this happens - that helps with context of what is going on.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    You should contact customer support - that is the proper process for dealing with these things. The crash logs are a little odd - there isn't really much of a stack trace in the logs.

    Please provide customer support with both the crash log and the CDS.log when this happens - that helps with context of what is going on.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information