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

[Phil Corbett]

Crashed when signing into empathy again.

phil@ubuntu:~$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

phil@ubuntu:~$ apt-cache policy telepathy-mission-control-5
telepathy-mission-control-5:
  Installed: 1:5.12.0-0ubuntu2
  Candidate: 1:5.12.0-0ubuntu2
  Version table:
 *** 1:5.12.0-0ubuntu2 0
        500 http://gb.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-mission-control-5 1:5.12.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sat Apr 14 13:50:46 2012
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic-pae root=UUID=BE762CEC762CA75D loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb703f0c0: mov 0x4(%edi),%edx
 PC (0xb703f0c0) ok
 source "0x4(%edi)" (0xc02ebc1c) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 realloc () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: mission-control-5 crashed with SIGSEGV in realloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #978046, 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.