mission-control-5 crashed with SIGSEGV in __GI___libc_free()

Bug #1025452 reported by Daniel Holbach
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
New
Medium
Unassigned

Bug Description

No idea what happened.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: telepathy-mission-control-5 1:5.12.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
Uname: Linux 3.5.0-4-generic x86_64
ApportVersion: 2.3-0ubuntu4
Architecture: amd64
CheckboxSubmission: 2f383a1679e8525d7196eb2518a1921f
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
CrashCounter: 1
Date: Mon Jul 16 23:45:36 2012
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110817)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-4-generic root=UUID=51ab960b-a2da-4841-98ce-c017f0582971 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f772c64d04c <__GI___libc_free+60>: mov (%rax),%rdi
 PC (0x7f772c64d04c) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 __GI___libc_free (mem=0x129bcb0) at malloc.c:2982
 ?? () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0
 tp_debug_sender_add_message () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0
 tp_debug_sender_add_message_vprintf () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0
Title: mission-control-5 crashed with SIGSEGV in __GI___libc_free()
UpgradeStatus: Upgraded to quantal on 2012-06-27 (19 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Daniel Holbach (dholbach) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI___libc_free (mem=0x129bcb0) at malloc.c:2982
 debug_message_free (msg=0x118f360) at debug-sender.c:148
 _tp_debug_sender_take (self=0x1159260, new_msg=0x12dca00) at debug-sender.c:368
 tp_debug_sender_add_message (self=self@entry=0x1159260, timestamp=<optimized out>, timestamp@entry=0x0, domain=domain@entry=0x441dae "mcd", level=level@entry=G_LOG_LEVEL_DEBUG, string=string@entry=0x123d310 "mcd_account_changed_property: called: Connection") at debug-sender.c:415
 tp_debug_sender_add_message_vprintf (self=0x1159260, timestamp=0x0, formatted=0x0, domain=0x441dae "mcd", level=G_LOG_LEVEL_DEBUG, format=<optimized out>, args=0x7fff8b2535b8) at debug-sender.c:454

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 telepathy-mission-control-5 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
tags: removed: apparmor
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.