Ubuntu
synergy package

synergyc 1.3.8 crashed with SIGABRT in GI_assert_fail(), but contiues to work anyway!?

Bug #927440 reported by Johan Domeij on 2012-02-06

132

This bug affects 15 people

Affects		Status	Importance	Assigned to	Milestone
	synergy (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

Synergyc 1.3.8 suddenly reports having crached, but mouse and keyboard continues working like before; indeed, this is written over synergy. Server is running on a ubuntu 10.10 x64 machine.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: synergy 1.3.8-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Mon Feb 6 05:01:58 2012
ExecutablePath: /usr/bin/synergyc
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/bin/synergyc --name acer1 192.168.1.3
Signal: 6
SourcePackage: synergy
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
__assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
CArchMultithreadPosix::closeMutex(CArchMutexImpl*) ()
CXWindowsEventQueueBuffer::~CXWindowsEventQueueBuffer() ()
Title: synergyc crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-02-06 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Johan Domeij (johan-domeij) wrote on 2012-02-06:

#1

Dependencies.txt Edit (765 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (854 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (135 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (9.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (814 bytes, text/plain; charset="utf-8")
Registers.txt Edit (761 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (3.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-06:

#2

StacktraceTop:
__GI___assert_fail (assertion=0x46d8c1 "status == 0", file=<optimized out>, line=289, function=<optimized out>) at assert.c:81
closeMutex (this=<optimized out>, mutex=<optimized out>) at /build/buildd/synergy-1.3.8/src/lib/arch/CArchMultithreadPosix.cpp:289
CArchMultithreadPosix::closeMutex (this=<optimized out>, mutex=0xd35b50) at /build/buildd/synergy-1.3.8/src/lib/arch/CArchMultithreadPosix.cpp:285
CXWindowsEventQueueBuffer::~CXWindowsEventQueueBuffer (this=0xd35a30, __in_chrg=<optimized out>) at /build/buildd/synergy-1.3.8/src/lib/platform/CXWindowsEventQueueBuffer.cpp:73
CXWindowsEventQueueBuffer::~CXWindowsEventQueueBuffer (this=0xd35a30, __in_chrg=<optimized out>) at /build/buildd/synergy-1.3.8/src/lib/platform/CXWindowsEventQueueBuffer.cpp:78

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-06: Stacktrace.txt

#3

Stacktrace.txt Edit (11.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-06: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (15.8 KiB, text/plain)

Changed in synergy (Ubuntu):
importance:	Undecided → Medium
summary:	- synergyc 1.3.8 crashed with SIGABRT in raise(), but contiues to work - anyway!? + synergyc 1.3.8 crashed with SIGABRT in __GI___assert_fail(), but + contiues to work anyway!?
tags:	removed: need-amd64-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-02-15:

#5

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in synergy (Ubuntu):
status:	New → Confirmed

Apport retracing service (apport) on 2012-06-26

tags:

added: quantal

Apport retracing service (apport) on 2012-09-26

tags:

added: bugpattern-needed

Maarten Lankhorst (mlankhorst) on 2012-10-01

visibility:

private → public

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.