• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. IC613 crashing in linux

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 125
  • Views 15024
  • 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
tkhan over 15 years ago

 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.

 

  • crash.txt
  • View
  • Hide
  • Cancel
Parents
  • tkhan
    tkhan over 15 years ago

    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

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • tkhan
    tkhan over 15 years ago

    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

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information