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,

    The lock file shouldn't present a problem. The way that locking works is that when you next run virtuoso and it wants to try to lock the same file, it will look in the .cdslck file to see what machine the process is running, and the process id of the locking process. It will then ask to find out if that process is still running or not. If that process isn't running any more, then the lock will be reclaimed.

    As for the crash when you open any schematic, that's more of a concern. Which Virtuoso version are you using? (what does "virtuoso -W" report at the UNIX prompt?).

    Regards,

    Andrew

Reply
  • Andrew Beckett

    Sanjay,

    The lock file shouldn't present a problem. The way that locking works is that when you next run virtuoso and it wants to try to lock the same file, it will look in the .cdslck file to see what machine the process is running, and the process id of the locking process. It will then ask to find out if that process is still running or not. If that process isn't running any more, then the lock will be reclaimed.

    As for the crash when you open any schematic, that's more of a concern. Which Virtuoso version are you using? (what does "virtuoso -W" report at the UNIX prompt?).

    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.