Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 17837
  • 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

CDS.log problem

SteveRFIC

Hi,

I have a problem with CDS.log file.

When I run ADEXL sims with large number of corners, I  noticed that the CDS.log file size increases significantly, several GBs. sometimes when disk is not available, then simulation hangs.

If I open the CDS.log file, I saw lots of warning messages, like PARSER WARNING. I guess these lines filled up the CDS.log file quickly.

Is there a way we can tell Cadence not to put those warning messages into CDS.log file?

Or can we change the default location of the CDS.log file, so that I can put it at a place with larger disk size?

Thanks a lot!

Parents
  • Andrew Beckett

    I wouldn't really expect that, and I wouldn't expect lots of "PARSER WARNING" messages. You should contact customer support so that we can investigate.

    As a stop-gap, you can use the UNIX environment variable $CDS_LOG_PATH to specify the directory where the CDS.log files are written.

    Regards,

    Andrew.

  • SteveRFIC
    in reply to Andrew Beckett

    Thank you Andrew!

    The warnings are certainly not normal, as you suspected. It is due to some settings in ADEXL, for instance, writing frequency of 10000000000 instead of 10G will cause some integer overflow issues, which are reported in CDS.log as parser warnings.

    I have fixed the errors and things are fine now. It is good to know $CDS_LOG_PATH variable.

    Thanks for the quick help!

Reply
  • SteveRFIC
    in reply to Andrew Beckett

    Thank you Andrew!

    The warnings are certainly not normal, as you suspected. It is due to some settings in ADEXL, for instance, writing frequency of 10000000000 instead of 10G will cause some integer overflow issues, which are reported in CDS.log as parser warnings.

    I have fixed the errors and things are fine now. It is good to know $CDS_LOG_PATH variable.

    Thanks for the quick help!

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.