synergyc crashed with SIGSEGV in std::_Rb_tree_increment()

Bug #951756 reported by dobey
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synergy (Ubuntu)
New
Undecided
Unassigned

Bug Description

syngergyc keeps crashing on my laptop, a very short time after start-up. And it's not getting restarted when this happens, even though I've passed --restart to it. Presumably it's not handling the SEGV signal and restarting a new copy when it happens, which could be another bug.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: synergy 1.3.8-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Sat Mar 10 14:28:47 2012
ExecutablePath: /usr/bin/synergyc
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110322.1)
ProcCmdline: synergyc --restart lunatari
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
 PATH=(custom, user)
 TERM=xterm
 LC_COLLATE=C
SegvAnalysis:
 Segfault happened at: 0xb7594bf2 <_ZSt18_Rb_tree_incrementPSt18_Rb_tree_node_base+18>: mov 0x8(%eax),%edx
 PC (0xb7594bf2) ok
 source "0x8(%eax)" (0x8b0a75c8) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: synergy
StacktraceTop:
 std::_Rb_tree_increment(std::_Rb_tree_node_base*) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
 std::insert_iterator<std::map<unsigned short, CKeyMap::KeyItem const*, std::less<unsigned short>, std::allocator<std::pair<unsigned short const, CKeyMap::KeyItem const*> > > > std::set_difference<std::_Rb_tree_iterator<std::pair<unsigned short const, CKeyMap::KeyItem const*> >, std::_Rb_tree_iterator<std::pair<unsigned short const, CKeyMap::KeyItem const*> >, std::insert_iterator<std::map<unsigned short, CKeyMap::KeyItem const*, std::less<unsigned short>, std::allocator<std::pair<unsigned short const, CKeyMap::KeyItem const*> > > >, CKeyState::ButtonToKeyLess>(std::_Rb_tree_iterator<std::pair<unsigned short const, CKeyMap::KeyItem const*> >, std::_Rb_tree_iterator<std::pair<unsigned short const, CKeyMap::KeyItem const*> >, std::_Rb_tree_iterator<std::pair<unsigned short const, CKeyMap::KeyItem const*> >, std::_Rb_tree_iterator<std::pair<unsigned short const, CKeyMap::KeyItem const*> >, std::insert_iterator<std::map<unsigned short, CKeyMap::KeyItem const*, std::less<unsigned short>, std::allocator<std::pair<unsigned short const, CKeyMap::KeyItem const*> > > >, CKeyState::ButtonToKeyLess) ()
 CKeyState::updateModifierKeyState(unsigned short, std::multimap<unsigned int, CKeyMap::KeyItem, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, CKeyMap::KeyItem> > > const&, std::multimap<unsigned int, CKeyMap::KeyItem, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, CKeyMap::KeyItem> > > const&) ()
 CKeyState::fakeKeyDown(unsigned int, unsigned int, unsigned short) ()
 CServerProxy::keyDown() ()
Title: synergyc crashed with SIGSEGV in std::_Rb_tree_increment()
UpgradeStatus: Upgraded to precise on 2011-11-29 (101 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
dobey (dobey) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #926198, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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