Issue 1471 - Unrecoverable Error
Summary: Unrecoverable Error
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 638
Hardware: PC Windows NT
: P2 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@l10n
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-08-16 09:43 UTC by Unknown
Modified: 2003-09-08 16:56 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
The MS Word file cause OpenOffice Write GPF (71.50 KB, application/octet-stream)
2001-08-16 09:46 UTC, Unknown 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2001-08-16 09:43:57 UTC 
I have a MS Word 97 file, it can be opened by using MS Word 97.
It has 1 page only, it contains Header, Footer, & table with some 
text. When I open it using "OpenOffice Write", it displays a error 
message: "Unrecoverable Error has occured."

The file is attached in the message already, and below is the 
detail error information:

SOFFICE caused an invalid page fault in
module SW633MI.DLL at 0167:1e2f11ae.
Registers:
EAX=00e5d84c CS=0167 EIP=1e2f11ae EFLGS=00010202
EBX=00000400 SS=016f ESP=00e5d838 EBP=021af3d8
ECX=00e5dca4 DS=016f ESI=00000004 FS=1227
EDX=00d15698 ES=016f EDI=00000000 GS=1216
Bytes at CS:EIP:
8b 0f 3b ca 8d 4c 24 14 0f 94 c3 e8 82 64 d9 ff 
Stack dump:
0223a4bc 0223a4bc 00e5df68 0000042d 00d10006 00d15698 00e5dca4 02230be8 
02239564 0224ab2c 00000022 00c4f424 1e01761e 1e0875be 00e5df5c 1e50a3f8
Comment 1 Unknown 2001-08-16 09:46:30 UTC 
Created attachment 449 [details]
The MS Word file cause OpenOffice Write GPF
Comment 2 Unknown 2001-08-27 00:51:31 UTC 
The attachment opens fine under NT4.

Rob
Comment 3 stefan.baltzer 2001-08-28 14:33:19 UTC 
Reassigned to Michael.
Comment 4 michael.ruess 2001-08-30 17:11:22 UTC 
In a 638 it is fixed. The 633 crashed. The flag "OS" was set wrongly.
In the Windows dump message you can see that it was in a 633-dll.
Comment 5 michael.ruess 2001-08-30 17:12:23 UTC 
Fixed bug becomes closed...