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
  • Andrew Beckett

    Sanjay,

    You are worrying about the wrong thing. Whenever you start virtuoso, it will create a CDS.log file (typically in your home directory), and because virtuoso is writing it, it will lock it using the Cadence Locking System. This is what creates the CDS.log.cdslck file. This is so that if you start a second virtuoso, it will not try to write to the same log file - it will see that it's locked and create CDS.log.1 (and lock that). So these lock files are supposed to be created (and if it didn't, that would be a problem).

    Normally when either the file is closed or virtuoso exits, the lock is cleared. However, in the event of the crash, there's no chance to clean up the locks and so the lock files remain - but they are recoverable using the mechanism I described previously - there's no need to delete them.

    So you are confusing a symptom with the real problem - the fact that it crashes. You are using an unsupported version of Virtuoso, and it's highly likely that whatever problem is causing the crash has been resolved in the intervening time period. So my first suggestion would be to try a newer version, and if that's not successful, you should contact customer support (we'd need the crash log files with stack traces etc to help identify if it's known issue).

    By the way, it's generally considered bad practice to run applications (such as Virtuoso) as root. Too much danger of breaking your OS to run as root (you might accidentally delete things that are vital to the correct operation of the machine).

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Sanjay,

    You are worrying about the wrong thing. Whenever you start virtuoso, it will create a CDS.log file (typically in your home directory), and because virtuoso is writing it, it will lock it using the Cadence Locking System. This is what creates the CDS.log.cdslck file. This is so that if you start a second virtuoso, it will not try to write to the same log file - it will see that it's locked and create CDS.log.1 (and lock that). So these lock files are supposed to be created (and if it didn't, that would be a problem).

    Normally when either the file is closed or virtuoso exits, the lock is cleared. However, in the event of the crash, there's no chance to clean up the locks and so the lock files remain - but they are recoverable using the mechanism I described previously - there's no need to delete them.

    So you are confusing a symptom with the real problem - the fact that it crashes. You are using an unsupported version of Virtuoso, and it's highly likely that whatever problem is causing the crash has been resolved in the intervening time period. So my first suggestion would be to try a newer version, and if that's not successful, you should contact customer support (we'd need the crash log files with stack traces etc to help identify if it's known issue).

    By the way, it's generally considered bad practice to run applications (such as Virtuoso) as root. Too much danger of breaking your OS to run as root (you might accidentally delete things that are vital to the correct operation of the machine).

    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.