synergys crashed with SIGSEGV in std::_Rb_tree_increment()

Bug #530905 reported by komputes
0
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synergy (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: synergy

Do not know what caused the crash. Synergy is non-responsive from client for a while before apport error showed up.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Mar 2 14:17:11 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/synergys
Package: synergy 1.3.1-6ubuntu1
ProcCmdline: /usr/bin/synergys -f --config .quicksynergy/synergy.conf
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
SegvAnalysis:
 Segfault happened at: 0x32e775 <_ZSt18_Rb_tree_incrementPSt18_Rb_tree_node_base+37>: cmp 0xc(%edx),%eax
 PC (0x0032e775) ok
 source "0xc(%edx)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: synergy
StacktraceTop:
 std::_Rb_tree_increment(std::_Rb_tree_node_base*) ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: synergys crashed with SIGSEGV in std::_Rb_tree_increment()
Uname: Linux 2.6.32-15-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
komputes (komputes) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #501239, 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
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.