You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 28, 2021. It is now read-only.
Using gdb to save backtrace to /home/lek/.licq/licq.backtrace.gdb
Failed to start gdb: No such file or directory
pure virtual method called
terminate called without an active exception
gdb exited with exit code 134
Licq has encountered a fatal error.
Please report this error either by creating a new ticket athttps://github.com/licq-im/licq/issues or by sending an e-mail to themailing list [email protected] (you must be registered to beable to post, see http://groups.google.com/group/licq-dev).
To help us debug the error, please include a full description of what you did when the error occurred. Additionally, please include the following files (if they exist):
/home/lek/.licq/licq.backtrace
/home/lek/.licq/licq.backtrace.gdb
/home/lek/.licq/licq.debug_rw_mutex
Thanks, The Licq Team
pure virtual method called
terminate called without an active exception
Aborted (core dumped)
licq.debug_rw_mutex is old, 4 day ago:
time: 1425630197
Possible deadlock for thread 0x7f2991344700 trying to get a write lock on 'ICQ_277507035'
No thread holds the write lock
These threads hold the read lock: 0x7f299a5c3700
Need i install gdb and run bt for more detail information?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Linux myallod 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64 GNU/Linux
Licq 1.9.0-f271d55/SSL Compiled Mar 6 2015
licq: /home/lek/Downloads/src/licq/licq/src/thread/readwritemutex_debug.cpp:140: void Licq::ReadWriteMutex::Private::setReader(): Assertion `i == myNumReaders' failed.
Using gdb to save backtrace to /home/lek/.licq/licq.backtrace.gdb
Failed to start gdb: No such file or directory
pure virtual method called
terminate called without an active exception
gdb exited with exit code 134
Backtrace (saved in /home/lek/.licq/licq.backtrace):
licq() [0x5435e3]
/lib64/libc.so.6(+0x33540) [0x7fa11d6e6540]
/lib64/libc.so.6(gsignal+0x37) [0x7fa11d6e64b7]
/lib64/libc.so.6(abort+0x16a) [0x7fa11d6e788a]
/lib64/libc.so.6(+0x2c41d) [0x7fa11d6df41d]
/lib64/libc.so.6(+0x2c4d2) [0x7fa11d6df4d2]
licq(_ZN4Licq14ReadWriteMutex7Private9setReaderEv+0x72) [0x5c6582]
licq(_ZN4Licq14ReadWriteMutex8lockReadEv+0x55) [0x5c67a9]
licq(_ZNK4Licq8Lockable8lockReadEv+0x18) [0x511650]
licq(_ZN10LicqDaemon11UserManager10fetchOwnerERKN4Licq6UserIdEb+0x100) [0x57ac34]
licq(_ZN4Licq14OwnerReadGuardC2ERKNS_6UserIdE+0x26) [0x57b3a4]
/usr/local/lib/licq/licq_qt-gui.so(+0x17328e) [0x7fa1132fb28e]
/usr/local/lib/licq/licq_qt-gui.so(+0xb0287) [0x7fa113238287]
/usr/local/lib/licq/licq_qt-gui.so(+0xb33bc) [0x7fa11323b3bc]
/usr/local/lib/licq/licq_qt-gui.so(+0x1ab33a) [0x7fa11333333a]
/lib64/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x32c) [0x7fa111129d9c]
/usr/local/lib/licq/licq_qt-gui.so(+0x1ac528) [0x7fa113334528]
/usr/local/lib/licq/licq_qt-gui.so(+0xc3994) [0x7fa11324b994]
/usr/local/lib/licq/licq_qt-gui.so(+0x1ac2a8) [0x7fa1133342a8]
/lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x1e1) [0x7fa11112e491]
/lib64/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x8c) [0x7fa11188b9ac]
/lib64/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x2b8) [0x7fa111892408]
/lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8d) [0x7fa11111528d]
/lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x231) [0x7fa111118651]
/lib64/libQtCore.so.4(+0x1b5233) [0x7fa111144233]
/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x24d) [0x7fa1108a371d]
/lib64/libglib-2.0.so.0(+0x49a08) [0x7fa1108a3a08]
/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fa1108a3abc]
/lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5d) [0x7fa11114437d]
/lib64/libQtGui.so.4(+0x26b3a6) [0x7fa11192f3a6]
/lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x41) [0x7fa111113de1]
/lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x1a5) [0x7fa111114145]
/lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x99) [0x7fa1111196e9]
/usr/local/lib/licq/licq_qt-gui.so(+0xaea02) [0x7fa113236a02]
/usr/local/lib/licq/licq_qt-gui.so(+0xc2e7a) [0x7fa11324ae7a]
licq(_ZN10LicqDaemon14PluginInstance16startThreadEntryEPv+0x82) [0x5b1628]
licq() [0x5b1a4a]
/lib64/libpthread.so.0(+0x7374) [0x7fa11f6f9374]
/lib64/libc.so.6(clone+0x6d) [0x7fa11d79b27d]
Attempting to generate core file.
Licq has encountered a fatal error.
Please report this error either by creating a new ticket athttps://github.com/licq-im/licq/issues or by sending an e-mail to themailing list [email protected] (you must be registered to beable to post, see http://groups.google.com/group/licq-dev).
To help us debug the error, please include a full description of what you did when the error occurred. Additionally, please include the following files (if they exist):
/home/lek/.licq/licq.backtrace
/home/lek/.licq/licq.backtrace.gdb
/home/lek/.licq/licq.debug_rw_mutex
Thanks, The Licq Team
pure virtual method called
terminate called without an active exception
Aborted (core dumped)
licq.debug_rw_mutex is old, 4 day ago:
time: 1425630197
Possible deadlock for thread 0x7f2991344700 trying to get a write lock on 'ICQ_277507035'
No thread holds the write lock
These threads hold the read lock: 0x7f299a5c3700
Need i install gdb and run bt for more detail information?
The text was updated successfully, but these errors were encountered: