Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 5634
  • 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

Warning envSetval: Can't set the value of variable 'pathPurposeList', in tool......

ChrisUOB

Hi,

I am getting a series of warnings upon initialisation of Virtuoso. All errors are in the CIW window. All of the same type as below:

""Warning envSetval: Can't set the value of variable 'pathPurposeList', in tool......""

I have tried using "virtuoso -nocdsinit &" and all warnings go away but this generates a series of other warnings when new schematics are created or opened. I have looked in the cdsinit and cdsenv files but nothing I can see (in my limited experience) as obviously wrong.

Wondered if anyone could spot something wrong.

All files and CIW output attached.

Parents
  • Andrew Beckett

    Really need to see the specific (and complete) message - you've just given a bit of the message (the tool mentioned in the warning). However, from that, I've seen that this was a layoutXL cdsenv setting in the IC5141 release, but which doesn't exist in subsequent releases. If I have the line:

    layoutXL pathPurposeList string "drawing net pin"

    in my ~/.cdsenv file then I get this in the CIW:

    *WARNING* envSetVal: Can't set the value of variable 'pathPurposeList',
    in tool[.partition] 'layoutXL' - it has not been registered.

    If the warnings go away when you use -nocdsinit, then it's probably that you've got some code in the .cdsinit file which is doing an envSetVal or using envLoadFile to load a .cdsenv file. 

    One way to try to debug it might be to use:

    procedure(CCFdebugWhereSet(toolPartition varName oldValue newValue)}
      when(varName=="pathPurposeList"
        printf("ENV SET: %L %L was %L now %L\n" toolPartition varName oldValue newValue)
        stacktrace()
      )
      t
    )
    envRegSetTrigger("layoutXL" 'CCFdebugWhereSet)

    You'd have to run "virtuoso -nocdsinit" then define this code, and then load the .cdsinit file it would have loaded otherwise. You'd have to adapt the code for each env var you're trying to track down.

    Hope that helps.

    Regards,

    Andrew.

  • Andrew Beckett
    in reply to Andrew Beckett

    Chris and I looked at this offline and located which file was causing the problem - turned out to be an old cdsenv file from a previous release was being loaded from the .cdsinit .

    Andrew.

Reply
  • Andrew Beckett
    in reply to Andrew Beckett

    Chris and I looked at this offline and located which file was causing the problem - turned out to be an old cdsenv file from a previous release was being loaded from the .cdsinit .

    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.