virtuoso Segmentation fault

Hi likelike

Instead of upgrading to IC615, would you please upgrade to the latest version IC616-500-2? I think it should solve your problem.

Best regards
Quek

When I try to open any schematic in Virtuoso, it closes and showing "Segmentation fault Virtuoso" in terminal window. It also creates CDS.log.cdslck file in root directory. How to release this lock?

Thanks,

Sanjay

Sanjay,

The lock file shouldn't present a problem. The way that locking works is that when you next run virtuoso and it wants to try to lock the same file, it will look in the .cdslck file to see what machine the process is running, and the process id of the locking process. It will then ask to find out if that process is still running or not. If that process isn't running any more, then the lock will be reclaimed.

As for the crash when you open any schematic, that's more of a concern. Which Virtuoso version are you using? (what does "virtuoso -W" report at the UNIX prompt?).

Regards,

Andrew

Mr. Andrew,

Thanks for your reply. I am using Virtuoso IC6.1.5.500.14 .  Actually Virtuoso crash happened yesterday when I was viewing the circuit in Virtuoso XL. After that Whenever I try to open the circuit in Virtuoso, it closes and generate CDS.log.cdslck file in root. If I delete this file and try to open the circuit again, cdslck file is generated again. The lock is not fixed only to a particular circuit. I could not open any of the circuit in my system.  I show below the contents of CDS.log.cdslck file for your reference. How to rectify this?

#
# Edit Lock-Stake file. CAUTION: Please do not change.
#
# Information about current Edit Lock Owner.
#
LockStakeVersion               1.1
LoginName                      root
HostName                       localhost.localdomain
ProcessIdentifier              10431
ProcessCreationTime_UTC        1470302066
ProcessCreationTime_Readable   Thu Aug  4 14:44:26 2016 IST
AppIdentifier                  /cad/cadence/IC615ISR_lnx86/tools.lnx86/dfII/bin/32bit/virtuoso
OSType                         lnx86
ReasonForPlacingEditLock       Set lock by hiiLockFile
FilePathUsedToEditLock         /root/CDS.log
TimeEditLocked                 Thu Aug  4 14:44:26 2016 IST

Regards,

Sanjay

Sanjay,

You are worrying about the wrong thing. Whenever you start virtuoso, it will create a CDS.log file (typically in your home directory), and because virtuoso is writing it, it will lock it using the Cadence Locking System. This is what creates the CDS.log.cdslck file. This is so that if you start a second virtuoso, it will not try to write to the same log file - it will see that it's locked and create CDS.log.1 (and lock that). So these lock files are supposed to be created (and if it didn't, that would be a problem).

Normally when either the file is closed or virtuoso exits, the lock is cleared. However, in the event of the crash, there's no chance to clean up the locks and so the lock files remain - but they are recoverable using the mechanism I described previously - there's no need to delete them.

So you are confusing a symptom with the real problem - the fact that it crashes. You are using an unsupported version of Virtuoso, and it's highly likely that whatever problem is causing the crash has been resolved in the intervening time period. So my first suggestion would be to try a newer version, and if that's not successful, you should contact customer support (we'd need the crash log files with stack traces etc to help identify if it's known issue).

By the way, it's generally considered bad practice to run applications (such as Virtuoso) as root. Too much danger of breaking your OS to run as root (you might accidentally delete things that are vital to the correct operation of the machine).

Regards,

Andrew.

Hi Sanjay,

You are running as user root. That was the bad practice thing - not the directory you're running it.

I didn't say anything about the crash being recoverable. I said that the lock can be recovered; essentially Virtuoso has a stranded-lock recovery mechanism which I described earlier in this thread - 

Replied to: virtuoso Segmentation fault

Sanjay, The lock file shouldn't present a problem. The way that locking works is that when you next run virtuoso and it wants to try to lock the same file, it will look in the .cdslck file to see what…

By Andrew Beckett over 9 years ago in Cadence Technology Forums > Custom IC Design

So what I meant was even if the CDS.log.cdslck file is left behind after the crash, the next time you run virtuoso (provided the previous process has really exited), Virtuoso should be able to reclaim the lock on CDS.log for the new process without you needing to delete it.

For the crash though, you need to either switch to a newer version (almost certainly, because it's a bug) or go via customer support so we can understand why it is crashing and if there's a fix.

Regards,

Andrew.