Stats

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

IC613 crashing in linux

tkhan

 Hi,

My colleauge and I experience frequent crashing (several times a day) when using ADE-L in IC613 sub-version IC6.1.3.500.14. For example, I tried to open the Direct Plot form just now and virtuoso crashed and created panic files for the open cellview. What could be causing this? The end of the log file is attached.

 

  • Hi tkhan

    For crash issues, a reproducible testcase would be required. It would be best if you can report this to your local Cadence support. As a workaround, I think perhaps we can try the following:

    a. Try IC613.500.15
    b. Open results brower (Tools->Results Browser) and plot signal using it
    c. Try plotting the same signal using ade-XL. The bug might not be present in ade-XL

    IC614 would be released in Dec. If the above does not work, hopefully IC614 can solve the problem. : )

    Best regards
    Quek

  • Hi Quek,

    The crash is not reproducable, it seems random. The only thing the crashes have in common is that they involve different actions in ADE, the direct plot form was just an example. We have IC613 sub-version IC6.1.3.500.2 for Solaris which doesn't have the crashing issue. I will try upgrading to IC613.500.15 tomorrow.

    BTW we get the following errors in terminal, they come up when performing various functions in ADE. Not sure if its a Cadence issue or a Linux issue:

    Locking assertion failure.  Backtrace:
    #0 /usr/lib/libxcb-xlib.so.0 [0x329767]
    #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0x32990e]
    #2 /usr/lib/libX11.so.6 [0x4d240e9]
    #3 /usr/lib/libX11.so.6(XQueryTree+0x25) [0x4d12655]
    #4 /CMC/tools/cadence/IC-6.1.3/tools/dfII/bin/32bit/virtuoso [0xc0633a2]
    #5 /usr/lib/libX11.so.6(XCheckIfEvent+0x94) [0x4cf6d74]
    #6 /CMC/tools/cadence/IC-6.1.3/tools/dfII/bin/32bit/virtuoso(_Z19hiiFlushWidgetEventP7QWidget+0x3f) [0xc0632df]
    #7 /CMC/tools/cadence/IC-6.1.3/tools/dfII/bin/32bit/virtuoso(_ZN16HiQConsoleWindow9updateLogEv+0x131) [0xc100d81]
    #8 /CMC/tools/cadence/IC-6.1.3/tools/dfII/bin/32bit/virtuoso(_ZN16HiQConsoleWindow11qt_metacallEN11QMetaObject4CallEiPPv+0xb4) [0xc12b5c4]
    #9 /CMC/tools/cadence/IC-6.1.3/tools/dfII/bin/32bit/virtuoso(_ZN6HiQCIW11qt_metacallEN11QMetaObject4CallEiPPv+0x2f) [0xc12b44f]
    #10 /CMC/tools/cadence/IC-6.1.3/tools/QT/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x605) [0x76e7b25]
    #11 /CMC/tools/cadence/IC-6.1.3/tools/QT/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x3c) [0x76e848c]
    #12 /CMC/tools/cadence/IC-6.1.3/tools/QT/lib/libQtCore.so.4(_ZN6QTimer7timeoutEv+0x33) [0x7705c53]
    #13 /CMC/tools/cadence/IC-6.1.3/tools/QT/lib/libQtCore.so.4(_ZN6QTimer10timerEventEP11QTimerEvent+0x3e) [0x76efd3e]
    #14 /CMC/tools/cadence/IC-6.1.3/tools/QT/lib/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x40f) [0x76e688f]
    #15 /CMC/tools/cadence/IC-6.1.3/tools/QT/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x17f) [0x1e243df]
    #16 /CMC/tools/cadence/IC-6.1.3/tools/QT/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x182) [0x1e26df2]
    #17 /CMC/tools/cadence/IC-6.1.3/tools/dfII/bin/32bit/virtuoso(_Z20qmotif_timer_handlerPvPm+0x1cb) [0xc14121b]
    #18 /usr/lib/libXt.so.6 [0x753a05a]
    #19 /usr/lib/libXt.so.6(XtAppNextEvent+0xad) [0x753a18d]

    I found more about this here: http://www.edaboard.com/ftopic320216.html

  • Hi tkhan

    IC613.500.16 has just been released. Please use this version instead. I am also not sure if this is a Virtuoso or linux issue. Need some troubleshooting to determine this. : )

    Best regards
    Quek

  •  Thanks Quek, downloading IC613.500.16 as we speak. Hopefully this solves the problem.

  • If it doesn't, please do contact Cadence Customer support. I did some searches based on the stack traces you posted, but it didn't seem to be anything reported so far... So the more info we can get, the better.

    Regards,

    Andrew

  • One of the nice new features in IC614 is that it creates a crash log upon crashing, I suppose these are what I should be sending to Cadence Customer Support. Is Sourcelink the only way to create support requests? I can't create an account for myself since we have a university license so only my network admin can access sourcelink, I'd prefer to be corresponding with customer support since I'm the one using the tools.

  • Hi Tarek,

    Unfortunately I can't give much advice because I don't know how the university program works in Canada (or North America in general). You may be able to send emails to support@cadence.com - but I don't know. Your network admin may know the details.

    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.