Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Word 6.0/95 document open fails with SIGBUS | ||||||
---|---|---|---|---|---|---|---|
Product: | Writer | Reporter: | mrauch-openoffice | ||||
Component: | code | Assignee: | caolanm | ||||
Status: | CLOSED FIXED | QA Contact: | issues@www <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P1 (highest) | CC: | issues | ||||
Version: | 619 | ||||||
Target Milestone: | --- | ||||||
Hardware: | Sun | ||||||
OS: | NetBSD | ||||||
Issue Type: | PATCH | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
mrauch-openoffice
2001-04-06 13:15:19 UTC
Created attachment 131 [details]
patch for bug
I'll just steal this out of the queue for myself. Attached patch looks good, checked in. Rev 1.12 of ww8scan.cxx Just reopening for a sec - can the patch be safely applied to 625? Something on the viability of 1.11 inside 625 would also be interesting looking at the number of bug ids.. The last applied patch on its own is certainly good for 625. The r1.11 or ww8scan.cxx along with r1.8 of ww8scan.hxx contain my "ultimate" patch to finally make fastsaved files work correctly. I *believe* that in isolation they should be good for 625, but I cannot guarantee it because I applied a number of nips and tucks to some of the other files around the same time that if not also included for OO625 might result in undefined behaviour. I reckon that they are ok though. Am practically sitting beside Sander now, so cubicle command decision not to risk fastsave fixes version for 625 taken. Closed long ago I added a target milestone just to help me for my statistics :-) |