• 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 SKILL
  3. Location of skill function definition

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 145
  • Views 19670
  • 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

Location of skill function definition

frankliu
frankliu over 9 years ago

Given a particular function, say foo(), I would like to know where it is defined.

There is a long list of .il functions that are loaded during initialization of virtuoso, so I am looking for a function that

1) returns the file path where the foo() was defined

2) in case of multiple definitions in different files, give the order they are loaded/overwritten

Notes:

I looked a couple of options such as whereIs(foo), error: cannot get source information (installed debugger)

startFinder(?funcName "foo"),  error: trouble connecting to cdsFinder

  • Cancel
Parents
  • fatcat1206
    fatcat1206 over 9 years ago

    Hi Andrew

    Thank you for the explanation.

    It's clear to me about the reason behind.

    I learned the "printstruct" function when reading the "SKILL Language User Guide" about the "Data Structure".

    I just open the document again, and find "For debugging" in the text. But on that moment, these words do not bring me attention. And I did not realize what trouble it can bring to me. (My mail boxed was exploded that day, as a lot colleges complained that I occupied all the license.)

    I was wondering should the risk be mentioned for "printstruct" in the "SKILL Language User Guide", and put a note that the license should be released later on manually. For me, the "SKILL Language User Guide" is the first document I read when I learn SKILL, I can not distinguish the difference between debugging functions and function-level development at that moment. Actually, I just know there are some functions dedicated for debugging. A lot of thing needs to be learned:)

    Best Regards

    Yi

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • fatcat1206
    fatcat1206 over 9 years ago

    Hi Andrew

    Thank you for the explanation.

    It's clear to me about the reason behind.

    I learned the "printstruct" function when reading the "SKILL Language User Guide" about the "Data Structure".

    I just open the document again, and find "For debugging" in the text. But on that moment, these words do not bring me attention. And I did not realize what trouble it can bring to me. (My mail boxed was exploded that day, as a lot colleges complained that I occupied all the license.)

    I was wondering should the risk be mentioned for "printstruct" in the "SKILL Language User Guide", and put a note that the license should be released later on manually. For me, the "SKILL Language User Guide" is the first document I read when I learn SKILL, I can not distinguish the difference between debugging functions and function-level development at that moment. Actually, I just know there are some functions dedicated for debugging. A lot of thing needs to be learned:)

    Best Regards

    Yi

    • 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