Bug 674331 - [abrt] empathy-2.32.2-1.fc14: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
Summary: [abrt] empathy-2.32.2-1.fc14: Process /usr/bin/empathy was killed by signal 1...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: empathy
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7bddc42665e3419b205a23704a4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-01 14:14 UTC by Marcel
Modified: 2011-02-18 12:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-01 15:22:29 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (531 bytes, text/plain)
2011-02-01 14:14 UTC, Marcel 		no flags Details
Backtrace (48.72 KB, text/plain)
2011-02-18 12:48 UTC, Baptiste AGASSE 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Marcel 2011-02-01 14:14:12 UTC 
abrt version: 1.1.14
architecture: x86_64
cmdline: /usr/bin/empathy
component: empathy
executable: /usr/bin/empathy
kernel: 2.6.35.10-74.fc14.x86_64
package: empathy-2.32.2-1.fc14
reason: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1296568744
uid: 500

backtrace
-----
[New Thread 4207]
[New Thread 4211]
[New Thread 4282]
[Thread debugging using libthread_db enabled]
Core was generated by `/usr/bin/empathy'.
Program terminated with signal 11, Segmentation fault.
#0  __strcmp_ssse3 () at ../sysdeps/x86_64/strcmp.S:213

Timeout exceeded: 60 second, killing gdb
Debuginfo absent: 623dc17ab4fbf28ae6b1351fe5fd0c3fa16cf341
Debuginfo absent: 8ad15ff2f9d35fc85c2017f0f5930251cbc07a17
Debuginfo absent: ba216ebb5a22011a4930f1b78ed9614a2b2ab5e3
Debuginfo absent: fee707d40d67cbc9fcaf8f91bfb3b6cc12243137

How to reproduce
-----
1. Nothing special
2.
3.
Comment 1 Marcel 2011-02-01 14:14:16 UTC 
Created attachment 476405 [details]
File: backtrace
Comment 2 Brian Pepple 2011-02-01 14:56:25 UTC 
Do you have a backtrace that is complete? This one doesn't provide enough information to figure out what's going on.
Comment 3 Marcel 2011-02-01 15:11:04 UTC 
Sorry i have nothing else :(
Comment 4 Brian Pepple 2011-02-01 15:22:29 UTC 
Closing for now since there is not enough info, but if you reproduce and can get some more information, please re-open. Thanks.
Comment 5 Baptiste AGASSE 2011-02-18 12:48:23 UTC 
Created attachment 479493 [details]
Backtrace
Note You need to log in before you can comment on or make changes to this bug.