• 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 Design
  3. IC5141usr6 on CentOS 4 in VMware

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 126
  • Views 14709
  • 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

IC5141usr6 on CentOS 4 in VMware

beschorn
beschorn over 14 years ago
Hi, I have a question regarding my installation of IC5141 in VMware: there is a long waiting circle, after every command I do (open a cell, creating a path, place am instance and so on). I thought, maybe there is a problem of the network connection to the license server, but even if I open cells in Read mode, I have the same problem. Is there a way, to get a log of messages from icfb (not the CDS.log), or is there a kind of debug option implemented? Configuration: IC5141usr6 installation OS: CentOS 4 (32bit) running in VMware Player 3.0.1 License server connected via network LAN Host System: Win7 64 bit Thanks for your help
  • Cancel
Parents
  • dmay
    dmay over 14 years ago

    If you have a Skill Development license you can try to see what commands are causing delays by using tracef. I've debugged this kind of problem before by running tracef(t) in the CIW, then issuing the command or opening a cell. LOTS of data will be output to your CDS.log file, but often times, you can see the command in the CIW where Cadence is hanging. Most commands will fly by in the CIW, but those that hang will appear long enough for you to read them. Once you Cadence finishes processing the command, you can turn off the trace with untrace().

    Derek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • dmay
    dmay over 14 years ago

    If you have a Skill Development license you can try to see what commands are causing delays by using tracef. I've debugged this kind of problem before by running tracef(t) in the CIW, then issuing the command or opening a cell. LOTS of data will be output to your CDS.log file, but often times, you can see the command in the CIW where Cadence is hanging. Most commands will fly by in the CIW, but those that hang will appear long enough for you to read them. Once you Cadence finishes processing the command, you can turn off the trace with untrace().

    Derek

    • 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