Stats

  • Locked Locked
  • Replies 8
  • Subscribers 127
  • Views 24863
  • 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

virtuoso Segmentation fault

likelike

 To whom it may help

Recently ,we got  Virtuoso ic614 (sub-version IC6.1.4.500.6 (32-bit addresses)) installed on a new RHEL6 machines.

We follow the previous experience, and with all the ncessary packages intalled , such as:

libXp, libXi, libXrender, libXt, libXext, libXtst, elfutils-libelf, glibc, gcc, ksh, Xorg-x11-fonts, openmotif, mesa-libGL, mesa-libGLU  etc...

Previously , these installation approach works fine , but just for this new machines installation, we got trouble with the invoking.

 

When we start the Cadence -virtuoso, it always fail, and directly give us a message:

 Segmentation fault  Virtuoso

 

IF we go to the /var/log/message, we can see following information:

 Sep 25 15:06:33 MESOPOTAMIA kernel: virtuoso[15837]: segfault at 0 ip (null) sp 00000000ffdee470 error 14 in libX11.so.6.3.0[101000+135000]
Sep 25 15:06:33 MESOPOTAMIA kernel: type=1701 audit(1380117993.265:49): auid=0 uid=0 gid=0 ses=125 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=15837 comm="virtuoso" sig=11

 

Furthermore , the kernel of linux is:

2.6.32-358.18.1.el6.x86_64 #1 SMP Tue Aug 27 14:23:09 CDT 2013 x86_64 x86_64 x86_64 GNU/Linux

 

 I don't know if any one can give us some hint for this information.

Or, is this means we have to upgrade to IC615.

Parents
  • SanjayNITT

    Mr. Andrew,

    Thanks for your reply. I am using Virtuoso IC6.1.5.500.14 .  Actually Virtuoso crash happened yesterday when I was viewing the circuit in Virtuoso XL. After that Whenever I try to open the circuit in Virtuoso, it closes and generate CDS.log.cdslck file in root. If I delete this file and try to open the circuit again, cdslck file is generated again. The lock is not fixed only to a particular circuit. I could not open any of the circuit in my system.  I show below the contents of CDS.log.cdslck file for your reference. How to rectify this?

    #
    # Edit Lock-Stake file. CAUTION: Please do not change.
    #
    # Information about current Edit Lock Owner.
    #
    LockStakeVersion               1.1
    LoginName                      root
    HostName                       localhost.localdomain
    ProcessIdentifier              10431
    ProcessCreationTime_UTC        1470302066
    ProcessCreationTime_Readable   Thu Aug  4 14:44:26 2016 IST
    AppIdentifier                  /cad/cadence/IC615ISR_lnx86/tools.lnx86/dfII/bin/32bit/virtuoso
    OSType                         lnx86
    ReasonForPlacingEditLock       Set lock by hiiLockFile
    FilePathUsedToEditLock         /root/CDS.log
    TimeEditLocked                 Thu Aug  4 14:44:26 2016 IST

    Regards,

    Sanjay


     

Reply
  • SanjayNITT

    Mr. Andrew,

    Thanks for your reply. I am using Virtuoso IC6.1.5.500.14 .  Actually Virtuoso crash happened yesterday when I was viewing the circuit in Virtuoso XL. After that Whenever I try to open the circuit in Virtuoso, it closes and generate CDS.log.cdslck file in root. If I delete this file and try to open the circuit again, cdslck file is generated again. The lock is not fixed only to a particular circuit. I could not open any of the circuit in my system.  I show below the contents of CDS.log.cdslck file for your reference. How to rectify this?

    #
    # Edit Lock-Stake file. CAUTION: Please do not change.
    #
    # Information about current Edit Lock Owner.
    #
    LockStakeVersion               1.1
    LoginName                      root
    HostName                       localhost.localdomain
    ProcessIdentifier              10431
    ProcessCreationTime_UTC        1470302066
    ProcessCreationTime_Readable   Thu Aug  4 14:44:26 2016 IST
    AppIdentifier                  /cad/cadence/IC615ISR_lnx86/tools.lnx86/dfII/bin/32bit/virtuoso
    OSType                         lnx86
    ReasonForPlacingEditLock       Set lock by hiiLockFile
    FilePathUsedToEditLock         /root/CDS.log
    TimeEditLocked                 Thu Aug  4 14:44:26 2016 IST

    Regards,

    Sanjay


     

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.