T. S. Collins Posted September 2, 2015 Posted September 2, 2015 [2015-09-01T21:52:27] INFO: entering screen [2015-09-01T21:52:27] INFO: clipboard was updated [2015-09-01T21:56:20] INFO: leaving screen [2015-09-01T21:56:27] INFO: entering screen [2015-09-01T22:06:05] INFO: leaving screen [2015-09-01T22:08:01] NOTE: server is dead [2015-09-01T22:08:01] WARNING: failed to connect to server: server is not responding Segmentation fault (core dumped) Happens at least once a day sometimes twice. Linux pestilence.nygenome.org 2.6.32-573.1.1.el6.centos.plus.x86_64 #1 SMP Sun Jul 26 00:52:05 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Bill Torpey Posted September 17, 2015 Posted September 17, 2015 Here's stack trace: Thread 4 (Thread 0x7f238eef3700 (LWP 29715)): Python Exception <type 'exceptions.ImportError'> No module named gdb.frames: #0 0x000000389fa0f535 in sigwait () from /lib64/libpthread.so.0 #1 0x000000000043dcc6 in ArchMultithreadPosix::threadSignalHandler(void*) () #2 0x000000389fa07a51 in start_thread () from /lib64/libpthread.so.0 #3 0x000000389f6e89ad in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f238e4f2700 (LWP 29716)): Python Exception <type 'exceptions.ImportError'> No module named gdb.frames: #0 0x000000389fa0ba0e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x000000000043e569 in ArchMultithreadPosix::waitCondVar(ArchCondImpl*, ArchMutexImpl*, double) () #2 0x0000000000483d35 in SocketMultiplexer::serviceThread(void*) () #3 0x0000000000486c2b in Thread::threadFunc(void*) () #4 0x000000000043ddb8 in ArchMultithreadPosix::doThreadFunc(ArchThreadImpl*) () #5 0x000000000043de9b in ArchMultithreadPosix::threadFunc(void*) () #6 0x000000389fa07a51 in start_thread () from /lib64/libpthread.so.0 #7 0x000000389f6e89ad in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f238eef5820 (LWP 29714)): Python Exception <type 'exceptions.ImportError'> No module named gdb.frames: #0 0x000000389fa0b63c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00000038a3242ee8 in _XReply () from /usr/lib64/libX11.so.6 #2 0x00000038a323ec2d in XSync () from /usr/lib64/libX11.so.6 #3 0x0000000000460003 in XWindowsUtil::ErrorLock::~ErrorLock() () #4 0x000000000046d5f6 in XWindowsScreenSaver::clearWatchForXScreenSaver() () #5 0x000000000046dc57 in XWindowsScreenSaver::~XWindowsScreenSaver() () #6 0x000000000046dcf9 in XWindowsScreenSaver::~XWindowsScreenSaver() () #7 0x000000000045d000 in XWindowsScreen::~XWindowsScreen() () #8 0x000000000045d1e9 in XWindowsScreen::~XWindowsScreen() () #9 0x000000000044f00d in synergy::Screen::~Screen() () #10 0x000000000044f069 in synergy::Screen::~Screen() () #11 0x000000000044ba29 in ClientApp::stopClient() () #12 0x000000000044c3a3 in ClientApp::mainLoop() () #13 0x000000000044bd1e in ClientApp::runInner(int, char**, ILogOutputter*, int (*)(int, char**)) () #14 0x000000000044fc92 in App::run(int, char**) () #15 0x0000000000437a23 in main () Thread 1 (Thread 0x7f2379bf5700 (LWP 6805)): Python Exception <type 'exceptions.ImportError'> No module named gdb.frames: #0 0x00000038a323ec07 in XSync () from /usr/lib64/libX11.so.6 #1 0x000000000045ff5b in XWindowsUtil::ErrorLock::install(void (*)(_XDisplay*, XErrorEvent*, void*), void*) () #2 0x0000000000460a92 in XWindowsUtil::atomToString(_XDisplay*, unsigned long) () #3 0x0000000000463de6 in XWindowsClipboard::icccmFillCache() () #4 0x0000000000465ebf in XWindowsClipboard::doFillCache() () #5 0x0000000000465f8b in XWindowsClipboard::has(IClipboard::EFormat) const () #6 0x0000000000470fb0 in IClipboard::copy(IClipboard*, IClipboard const*, unsigned int) () #7 0x0000000000455f5a in Client::sendClipboard(unsigned char) () #8 0x00000000004560ba in Client::sendClipboardThread(void*) () #9 0x0000000000486c2b in Thread::threadFunc(void*) () #10 0x000000000043ddb8 in ArchMultithreadPosix::doThreadFunc(ArchThreadImpl*) () #11 0x000000000043de9b in ArchMultithreadPosix::threadFunc(void*) () #12 0x000000389fa07a51 in start_thread () from /lib64/libpthread.so.0 #13 0x000000389f6e89ad in clone () from /lib64/libc.so.6
Bill Torpey Posted September 18, 2015 Posted September 18, 2015 Also, note that the crashes associated with stack trace are running against OSX server running 1.7.4 of synergy
Recommended Posts
Archived
This topic is now archived and is closed to further replies.