Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 10115
  • 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

how to add printf statement to .cdsenv file?

KurtKimber1

Is there a way to put a printf statement in a .cdsenv file?  Thanks

Parents
  • Andrew Beckett

    No. Why would you want to? It's a file which is not code - it's a specific format with just environment variable settings.

    Andrew

  • KurtKimber1
    in reply to Andrew Beckett

    We load several .cdsenv files and I would like to add a printf statement for debugging purposes.

Reply
  • KurtKimber1
    in reply to Andrew Beckett

    We load several .cdsenv files and I would like to add a printf statement for debugging purposes.

Children
  • Andrew Beckett
    in reply to KurtKimber1

    Unfortunately tracking them down can be slightly tricky. I tend to use the following approaches:

    1. Use "cdswhich -all .cdsenv" (to list all that would be loaded via the Cadence Setup File (setup.loc) mechanism; that's not always enabled, but a good way to find them if they are)
    2. Use trace(envLoadFile) (perhaps using "virtuoso -nocdsinit" to allow you to avoid the auto-loading of the .cdsinit so you can do the trace before then loading the .cdsinit manually)
    3. Use envRegSetTrigger to define a trigger function to be called when a specific tool's env var is set, and then printing out some context information at that point to try to pinpoint what is happening).

    This article might also give some useful pointers (or some of the articles it points to): Debugging Virtuoso Session – Basic Tips and Frequently Asked Questions

    Andrew

  • KurtKimber1
    in reply to Andrew Beckett

    Good stuff, as usual, Andrew.   Thanks very much

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.