empathy crashed with SIGSEGV in _empathy_marshal_VOID__UINT_UINT()

Bug #806124 reported by Bilal Shahid
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Expired
Medium
Unassigned

Bug Description

i dnt know

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: empathy 3.1.2.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
Uname: Linux 3.0-3-generic i686
Architecture: i386
Date: Tue Jul 5 23:47:23 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110531.1)
ProcCmdline: empathy
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x807d8ed: mov 0x14(%edi),%eax
 PC (0x0807d8ed) ok
 source "0x14(%edi)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 ?? ()
 _empathy_marshal_VOID__UINT_UINT ()
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in _empathy_marshal_VOID__UINT_UINT()
UpgradeStatus: Upgraded to oneiric on 2011-06-28 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Bilal Shahid (s9iper1) wrote :
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in empathy (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
tags: removed: need-i386-retrace
Revision history for this message
Bilal Shahid (s9iper1) wrote :

bil21al@bil21al-ThinkPad-T60:~$ gdb empathy
GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/empathy...(no debugging symbols found)...done.
(gdb)
(gdb)
(gdb) run
Starting program: /usr/bin/empathy
[Thread debugging using libthread_db enabled]
[New Thread 0xb6f2db70 (LWP 10601)]
[New Thread 0xb65ffb70 (LWP 10602)]
[Thread 0xb65ffb70 (LWP 10602) exited]
[Thread 0xb6f2db70 (LWP 10601) exited]

Program exited normally.
(gdb)

Revision history for this message
Pedro Villavicencio (pedro) wrote :

could you please try again? the log is empty and please next time attach it instead of doing copy & paste, thanks!.

Revision history for this message
Bilal Shahid (s9iper1) wrote :

i m not be able to gain it or may be i m not follow the right way of steps..is there any other way to find out the log file???

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for empathy (Ubuntu) because there has been no activity for 60 days.]

Changed in empathy (Ubuntu):
status: Incomplete → Expired
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.