friends-dispatcher crashed with SIGSEGV in ffi_call_unix64()

Bug #1294743 reported by piotrekw1
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
friends (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

actualisation

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: friends-dispatcher 0.2.0+14.04.20140217.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar 19 17:22:26 2014
ExecutablePath: /usr/bin/friends-dispatcher
InstallationDate: Installed on 2014-03-18 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140318)
InterpreterPath: /usr/bin/python3.4
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/friends-dispatcher -o
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=pl_PL
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f11c5b5abf0: cmp %rdi,0x18(%rdx)
 PC (0x7f11c5b5abf0) ok
 source "%rdi" ok
 destination "0x18(%rdx)" (0x00000017) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: friends
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-34m-x86_64-linux-gnu.so
 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-34m-x86_64-linux-gnu.so
Title: friends-dispatcher crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
piotrekw1 (piotrekw1) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7f11a0090b38, fn=0x7f11c16c40a0 <dee_model_get_position>, rvalue=rvalue@entry=0x7f11b8bbc8e0, avalue=0x7f11a006e980) at ../src/x86/ffi64.c:522
 _invoke_callable (callable_info=<optimized out>, cache=0x7f11a0090ad0, state=0x7f11b8bbc8f0) at ../../gi/pygi-invoke.c:38
 pygi_callable_info_invoke (info=<optimized out>, py_args=py_args@entry=0x7f11c37dcd88, kwargs=kwargs@entry=0x0, cache=0x7f11a0090ad0, user_data=user_data@entry=0x0) at ../../gi/pygi-invoke.c:732

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in friends (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in friends (Ubuntu):
status: New → Confirmed
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.