ekiga crashed with SIGSEGV in std::_Rb_tree_increment()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ekiga (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ekiga
ekiga was idle when crashed
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: ekiga 3.2.6-1ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelMo
Architecture: i386
CrashCounter: 1
Date: Sun Apr 18 17:29:40 2010
ExecutablePath: /usr/bin/ekiga
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100416)
ProcCmdline: ekiga
ProcEnviron:
LANG=en_CA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x5062762 <_ZSt18_
PC (0x05062762) ok
source "0x8(%edx)" (0x733c202a) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: ekiga
StacktraceTop:
std::_
Ekiga:
Avahi:
?? ()
avahi_
Title: ekiga crashed with SIGSEGV in std::_Rb_
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
It happens when the presence status of a "neighbor" changes