Bug 575626 - [abrt] crash in thunderbird-3.0.3-1.fc12: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
[abrt] crash in thunderbird-3.0.3-1.fc12: Process /usr/lib64/thunderbird-3.0/...
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: thunderbird (Show other bugs)
12
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
abrt_hash:aaedbfc741d9d8b169edfa03301...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-03-21 16:07 EDT by Roel van de Kraats
Modified: 2010-06-03 11:27 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-03 11:27:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (56.06 KB, text/plain)
2010-03-21 16:07 EDT, Roel van de Kraats
no flags Details

  None (edit)
Description Roel van de Kraats 2010-03-21 16:07:07 EDT
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/thunderbird-3.0/thunderbird-bin
comment: resume after suspend to ram
component: thunderbird
executable: /usr/lib64/thunderbird-3.0/thunderbird-bin
kernel: 2.6.32.9-70.fc12.x86_64
package: thunderbird-3.0.3-1.fc12
rating: 3
reason: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Roel van de Kraats 2010-03-21 16:07:10 EDT
Created attachment 401596 [details]
File: backtrace
Comment 2 Chris Campbell 2010-06-03 11:26:31 EDT
#2  <signal handler called>
No symbol table info available.
#3  0x00007faf6e44aa00 in ?? ()
No symbol table info available.
#4  0x0000000000000000 in ?? ()
No symbol table info available.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 3 Chris Campbell 2010-06-03 11:27:51 EDT
There is not enough information in that back-trace to attempt to troubleshoot this crash. I am closing this report; please feel free to re-open it if you disagree with my assessment.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Note You need to log in before you can comment on or make changes to this bug.