Stats

  • Locked Locked
  • Replies 9
  • Subscribers 144
  • Views 18018
  • 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

Trigger Warning at Virtuoso start up

wgtkan
*WARNING* (DEBASE-102068): No user triggers registered for viewType schematicSymbol.

*WARNING* (DEBASE-102068): No user triggers registered for viewType maskLayout.

*WARNING* (DEBASE-102068): No user triggers registered for viewType maskLayoutXL.

*WARNING* No application registered for prefix awv.

*WARNING* No application registered for prefix awv.

*WARNING* No application registered for prefix awv.

What are these warnings and how do I get rid of them? What do these mean? My IC version is IC6.1.5-64b.500.15

 

Thank you in advance.
Parents

  • In my earlier post in this thread, I included a link to another post which suggested that these are probably coming from a call to deUnRegUserTriggers() in a context file loaded from the .cdsinit. It's unlikely that they're in the bindkeys - unless there's a call to this function in leBindKeys.il or schBindKeys.il - which seems unlikely.

    The warnings are benign - although it is bad practice of the PDK to be unregistering the de triggers. This has been shown to break certain tools because they depend upon these triggers. In ancient history (IC446 and before) there used to be a limitation that you could only have one user trigger defined - but this was fixed over 10 years ago. So you really ought to contact IBM.

    If you can't track down where they are coming from, and want a quiet life for users (no warnings), you could always add this at the beginning of the .cdsinit before any of the PDK stuff is loaded:

    procedure(CCFdummy(args) t)
    deRegUserTriggers("maskLayout" 'CCFdummy)
    deRegUserTriggers("maskLayoutXL" 'CCFdummy)
    deRegUserTriggers("schematicSymbol" 'CCFdummy)

    Oh, hang on - you were asking about the "awv" messages (I got confused because you posted about the other warnings in another old thread). The awv warnings must be coming because of a call, somewhere, to an hiSetBindKey on "awv". You'll just have to hunt it down!

    Try running "virtuoso -nocdsinit" and then gradually load the files loaded from the .cdsinit - or comment out pieces of the .cdsinit and see the effect.  Again, the warnings won't cause any problems in practice.

    Regards,

    Andrew.

Reply

  • In my earlier post in this thread, I included a link to another post which suggested that these are probably coming from a call to deUnRegUserTriggers() in a context file loaded from the .cdsinit. It's unlikely that they're in the bindkeys - unless there's a call to this function in leBindKeys.il or schBindKeys.il - which seems unlikely.

    The warnings are benign - although it is bad practice of the PDK to be unregistering the de triggers. This has been shown to break certain tools because they depend upon these triggers. In ancient history (IC446 and before) there used to be a limitation that you could only have one user trigger defined - but this was fixed over 10 years ago. So you really ought to contact IBM.

    If you can't track down where they are coming from, and want a quiet life for users (no warnings), you could always add this at the beginning of the .cdsinit before any of the PDK stuff is loaded:

    procedure(CCFdummy(args) t)
    deRegUserTriggers("maskLayout" 'CCFdummy)
    deRegUserTriggers("maskLayoutXL" 'CCFdummy)
    deRegUserTriggers("schematicSymbol" 'CCFdummy)

    Oh, hang on - you were asking about the "awv" messages (I got confused because you posted about the other warnings in another old thread). The awv warnings must be coming because of a call, somewhere, to an hiSetBindKey on "awv". You'll just have to hunt it down!

    Try running "virtuoso -nocdsinit" and then gradually load the files loaded from the .cdsinit - or comment out pieces of the .cdsinit and see the effect.  Again, the warnings won't cause any problems in practice.

    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.