[Bug 913018] [NEW] sflphoned crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook()

Launchpad Bug Tracker 913018 at bugs.launchpad.net
Thu Mar 22 10:40:43 UTC 2012


You have been subscribed to a public bug by Whoopie (whoopie79):

This happens when trying to launch sflphone.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: sflphone-daemon 1.0.1-4.1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Fri Jan  6 21:13:27 2012
ExecutablePath: /usr/lib/sflphone/sflphoned
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120102)
ProcCmdline: /usr/lib/sflphone sflphoned
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f55284ea413 <_ZNSt8__detail15_List_node_base7_M_hookEPS0_+19>:	mov    %rdi,(%rax)
 PC (0x7f55284ea413) ok
 source "%rdi" ok
 destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: sflphone
StacktraceTop:
 std::__detail::_List_node_base::_M_hook(std::__detail::_List_node_base*) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 DBus::DefaultWatch::DefaultWatch(int, int, DBus::DefaultMainLoop*) () from /usr/lib/libdbus-c++-1.so.0
 DBus::BusWatch::BusWatch(DBus::Watch::Internal*, DBus::BusDispatcher*) () from /usr/lib/libdbus-c++-1.so.0
 DBus::BusDispatcher::add_watch(DBus::Watch::Internal*) () from /usr/lib/libdbus-c++-1.so.0
 ?? () from /usr/lib/libdbus-c++-1.so.0
Title: sflphoned crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: sflphone (Ubuntu)
     Importance: Medium
         Status: Confirmed


** Tags: amd64 apport-crash precise running-unity
-- 
sflphoned crashed with SIGSEGV in std::__detail::_List_node_base::_M_hook()
https://bugs.launchpad.net/bugs/913018
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list