Bug 562405 - [abrt] crash in openoffice.org-calc-1:3.1.1-19.14.fc12
Summary: [abrt] crash in openoffice.org-calc-1:3.1.1-19.14.fc12
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:cbc2ab77c6579386f2f87173587...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-06 14:22 UTC by Greg Overtoom
Modified: 2010-02-09 14:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-09 14:19:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.70 KB, text/plain)
2010-02-06 14:22 UTC, Greg Overtoom
no flags Details

Description Greg Overtoom 2010-02-06 14:22:09 UTC
abrt 1.0.4 detected a crash.

architecture: i686
cmdline: /usr/lib/openoffice.org3/program/scalc.bin -calc file:///home/Greg/Dropbox/Exercise_Log_2010.ods
component: openoffice.org
executable: /usr/lib/openoffice.org3/program/scalc.bin
kernel: 2.6.31.12-174.2.3.fc12.i686
package: openoffice.org-calc-1:3.1.1-19.14.fc12
rating: 0
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)

backtrace
-----
BFD: Warning: /var/cache/abrt/ccpp-1264734682-1911/coredump is truncated: expected core file size >= 86204416, found: 81985536.
[New Thread 1911]
[New Thread 1912]
[New Thread 1913]
Cannot access memory at address 0xb7754790

Thread 4 (Thread 1913):
#0  0x00f47416 in ?? ()
No symbol table info available.
#1  0x005d9f72 in ?? ()
No symbol table info available.
#2  0x00000000 in ?? ()
No symbol table info available.

Thread 3 (Thread 1912):
Cannot access memory at address 0xb76f92f8

Thread 2 (Thread 1911):
Cannot access memory at address 0xbfe5147c

Thread 1 (Thread 1916):
#0  0x04ac4f2a in ?? ()
No symbol table info available.
#1  0x02ad6f44 in ?? ()
No symbol table info available.
#2  0x091598a8 in ?? ()
No symbol table info available.
#3  0xb3727158 in ?? ()
No symbol table info available.
#4  0x029dca57 in ?? ()
No symbol table info available.
#5  0x091598a8 in ?? ()
No symbol table info available.
#6  0x00633630 in ?? ()
No symbol table info available.
#7  0x0915a1f0 in ?? ()
No symbol table info available.
#8  0x029dca0a in ?? ()
No symbol table info available.
#9  0x02ad6f44 in ?? ()
No symbol table info available.
#10 0x091598a8 in ?? ()
No symbol table info available.
#11 0xb37271c8 in ?? ()
No symbol table info available.
#12 0x029e49d3 in ?? ()
No symbol table info available.
#13 0x091598a8 in ?? ()
No symbol table info available.
#14 0x000010af in ?? ()
No symbol table info available.
#15 0xb37271ac in ?? ()
No symbol table info available.
#16 0xb37271a8 in ?? ()
No symbol table info available.
#17 0xb372717c in ?? ()
No symbol table info available.
#18 0x00000000 in ?? ()
No symbol table info available.
Cannot access memory at address 0xb7754790
No symbol table is loaded.  Use the "file" command.

How to reproduce
-----
1. Boot computer
2. Log in
3.

Comment 1 Greg Overtoom 2010-02-06 14:22:11 UTC
Created attachment 389278 [details]
File: backtrace

Comment 2 Caolan McNamara 2010-02-06 16:49:03 UTC
Unfortunately the backtrace is truncated. Do you know what you were doing at the time of the crash. Is it reproducible ?

Comment 3 Caolan McNamara 2010-02-09 14:19:04 UTC
Stack is busted, feel free to reopen this issue if you know how to reproduce this


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