ekiga crashed with SIGSEGV in PStringOptions::SetAt()

[Steve Langasek]

crashed when I was looking at my audio device settings.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: ekiga 3.3.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CheckboxSubmission: 017452a27eca3c8b498abbfa5ef91db9
CheckboxSystem: ecaaad6fa1e0799a0aa1126bf620f39e
Date: Wed Feb 8 09:02:07 2012
ExecutablePath: /usr/bin/ekiga
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: ekiga
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f971d3d92f6 <_ZN14PStringOptions5SetAtEPKcRK7PString+118>: mov 0xf0(%rax),%r14
 PC (0x7f971d3d92f6) ok
 source "0xf0(%rax)" (0x000000f0) not located in a known VMA region (needed readable region)!
 destination "%r14" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ekiga
StacktraceTop:
 PStringOptions::SetAt(char const*, PString const&) () from /usr/lib/libopal.so.3.10.2
 SIPEndPoint::AdjustToRegistration(OpalTransport const&, SIP_PDU&) () from /usr/lib/libopal.so.3.10.2
 SIP_PDU::SendResponse(OpalTransport&, SIP_PDU&, SIPEndPoint*) const () from /usr/lib/libopal.so.3.10.2
 SIPResponse::Send(OpalTransport&, SIP_PDU const&) () from /usr/lib/libopal.so.3.10.2
 SIPEndPoint::OnReceivedOPTIONS(OpalTransport&, SIP_PDU&) () from /usr/lib/libopal.so.3.10.2
Title: ekiga crashed with SIGSEGV in PStringOptions::SetAt()
UpgradeStatus: Upgraded to precise on 2011-11-08 (91 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src

[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 #869397, 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.

[Launchpad Janitor (janitor)]

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

[Russ Dill (russ-dill)]

It isn't very useful to mark a bug as a duplicate of a private bug, how can I track it?