Stats

  • Locked Locked
  • Replies 2
  • Subscribers 124
  • Views 14093
  • 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

find out which SKILL function is called in the background

sunilm123

I have a schematic , where if I select any of the instance and press Q (Edit Object properties)  ,  some function is getting called (Internal customization)  and it does the check n save of that schematic.

I am trying to figure out which function is called.

I have tried setting sstatus debugMode t  and sstatus stacktrace t , also enabled all the "log filters"  but that didn't help .

Is there any other pointers which I can try .

Parents
  • Andrew Beckett

    The brute force way would be to use trace(t) . I would probably adopt some more refined tracing myself, but then again I'd probably need to understand exactly at which step it occurred. I might start with tracing the schematic extraction type functions:

    trace(schExtractConn schCheck)

    and then if these show up as being triggered, I might then set breakpoints on them (using breakpt), invoking the command that triggers it, and then typing "where" in the CIW to find out the stack trace at the point the debugger has kicked in (type continue() to continue from the breakpoint).

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    The brute force way would be to use trace(t) . I would probably adopt some more refined tracing myself, but then again I'd probably need to understand exactly at which step it occurred. I might start with tracing the schematic extraction type functions:

    trace(schExtractConn schCheck)

    and then if these show up as being triggered, I might then set breakpoints on them (using breakpt), invoking the command that triggers it, and then typing "where" in the CIW to find out the stack trace at the point the debugger has kicked in (type continue() to continue from the breakpoint).

    Regards,

    Andrew.

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.