Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 16790
  • 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

Stopping a SKILL script

thomas1000

Is there a way to terminate a lengthy SKILL script without having to kill the Cadence process?

Parents

  • My experience is that control-c will do the job in between skill commands. However, if you have a command like dbGetTrueOverlaps that is taking a while to run because it was given too much area, the control-c will not work until that particular command completes. As long as your skill code is progressing from one command to the next the control-c works just fine.

    Derek

Reply

  • My experience is that control-c will do the job in between skill commands. However, if you have a command like dbGetTrueOverlaps that is taking a while to run because it was given too much area, the control-c will not work until that particular command completes. As long as your skill code is progressing from one command to the next the control-c works just fine.

    Derek

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.