Home > Community > Forums > Custom IC SKILL > Stopping a SKILL script

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 Stopping a SKILL script 

Last post Wed, Jan 23 2013 12:10 PM by Andrew Beckett. 3 replies.
Started by thomas1000 22 Jan 2013 01:58 PM. Topic has 3 replies and 787 views
Page 1 of 1 (4 items)
Sort Posts:
  • Tue, Jan 22 2013 1:58 PM

    Stopping a SKILL script Reply

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

    • Post Points: 20
  • Tue, Jan 22 2013 9:54 PM

    Re: Stopping a SKILL script Reply
    Normally hitting control C will do the job.
    • Post Points: 20
  • Wed, Jan 23 2013 6:32 AM

    • dmay
    • Top 25 Contributor
    • Joined on Thu, Jul 17 2008
    • Allen, TX
    • Posts 393
    • Points 7,415
    Re: Stopping a SKILL script 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

    • Post Points: 20
  • Wed, Jan 23 2013 12:10 PM

    Re: Stopping a SKILL script Reply

    Derek,

    Potentially that function could be enhanced to periodically call the check for ctrl-C to allow it to be interrupted (of course, it would need to clean up gracefully too) - if you want that, log a service request.

    We've just done this (for IC616 I think) for a few SKILL list processing functions where they could get stuck when processing circular lists, and it shouldn't impact performance if done properly.

    Regards,

    Andrew.

    • Post Points: 5
Page 1 of 1 (4 items)
Sort Posts:
Started by thomas1000 at 22 Jan 2013 01:58 PM. Topic has 3 replies.