telepathy-gabble crashed with SIGSEGV in gethostbyname2_r()

Bug #948298 reported by sl45sms
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-gabble (Ubuntu)
New
Undecided
Unassigned

Bug Description

On start, but everything works after just few seconds

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-gabble 0.15.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Tue Mar 6 21:04:40 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/telepathy-gabble
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
ProcCmdline: /usr/lib/telepathy/telepathy-gabble
SegvAnalysis:
 Segfault happened at: 0x7f49657f4bfe: lock xadd %eax,0x18(%rdi)
 PC (0x7f49657f4bfe) ok
 source "%eax" ok
 destination "0x18(%rdi)" (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: telepathy-gabble
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 gethostbyname2_r () from /lib/x86_64-linux-gnu/libc.so.6
Title: telepathy-gabble crashed with SIGSEGV in gethostbyname2_r()
UpgradeStatus: Upgraded to precise on 2012-03-02 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
sl45sms (sl45sms) wrote :
sl45sms (sl45sms)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #930345, 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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.