Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13547
  • 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

Ophaned .cdslck file with custom view type

bforejtAtTI

Version info: IC6.1.8-64b.500.10.EHF7015

I have created a custom view type but have a problem with orphaned .cdslck files.  The custom view type launches my own external application with a GUI interface for manipulating some proprietary files related to a specific schematic.  When the APP closes, the cdslck file is left in the database.

I have tried manually removing the .cdslck file on the linux command line but this creates a new problem.  After the manual deletion  the cdslck file is no longer created for that library, cell, view (LCV) combination for the Virtuoso session.  If I restart Virtuoso, the cdslck file can be recreated for the LCV.

Based upon this, I'm assuming that the Virtuoso session holds a reference to the LCV in memory and marks it as 'locked' and then when the user in the current session attempts to open the same LCV a second time it will skip the portion of the flow that creates the cdslck file. 

I found this by implementing code in skill that when on exit, the skill IPC module will 'clean up' the ophaned cdslck file.

My question is related to the proper procedure for opening and closing a custom view type.  Are there special commands to tell virtuoso to remove/release the cdslck?  We use DesignSync as or data management tool if that has any impact...

Regards,

  • bforejtAtTI

    Solved:

    I have found that using the skill command:  ddLockSet( lockObj "r") on application close removes the cdslck file.

  • Andrew Beckett
    in reply to bforejtAtTI

    A better way is to use ddLockFree(lockObj)

    See the code in How to create a text cellview using SKILL? for example (one of my code examples).

    Regards,

    Andrew.

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.