Stats

  • Locked Locked
  • Replies 1
  • Subscribers 124
  • Views 13327
  • 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

QRC crashes at Techgen step

Zach

Using Assura 4.1 and EXT9.1.4, we are seeing a Segmentation Fault from Techgen that causes QRC to crash.  We reported the problem to the fab vendor, and they replied saying they saw no problems at all and QRC completes for them.  We are both using the same versions and same rule decks.  An interesting difference was found in the two log files:

 My log
----------
*WARNING* at "Techgen -trans": The gate layer name allGate is duplicated with a
layer name defined in the process file Segmentation Fault

Their log
------------

*WARNING* at "Techgen -trans": The gate layer name allGate is duplicated with a
layer name defined in the process file (null), and therefore renamed to allGate_2.

 

The only known difference is that we are running Solaris 10 on UNIX and the fab vendor uses RH Linux.  Can anyone provide any insight into why this is happening and what can be done to fix it?  Thanks.

  • This appears to be the same issue that was fixed by CCR 902399 - from the CCR history it says:

    Capgen fails when printing: *WARNING* at "Techgen -trans": The gate layer name
allGate is duplicated with a layer name defined in the process file ??, and
therefore renamed to allGate_2. 

The "process file" name appears to be NULL. Linux compiler does substitute
(null) in this case while Sun compiler not.

    This was fixed in version EXT10.12.055, Version: EXT_10.1.2   (which is the second update release of EXT101 on downloads.cadence.com ) - so getting either this, the later update, or hotfix version should fix this. If it doesn't, then you should file a service request with customer support and reference this post.

    Regards,

    Andrew.

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.