Issue 88499 - crash opening ODF .odt created by OdfConverter
Summary: crash opening ODF .odt created by OdfConverter
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: DEV300m9
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: andreas.martens
QA Contact: issues@sw
Keywords: crash, regression
Depends on:
Reported: 2008-04-20 19:44 UTC by aziem
Modified: 2013-08-07 14:43 UTC (History)
2 users (show)

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

crashes DEV300_m9 but not OOo 2.4.0 (30.70 KB, application/vnd.oasis.opendocument.text)
2008-04-20 19:45 UTC, aziem
no flags Details
stack trace (13.09 KB, text/plain)
2008-04-20 19:47 UTC, aziem
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description aziem 2008-04-20 19:44:49 UTC
OOo 2.4.0 opens this document fine but OOO 3.0 DEV300_m9 crashes. I will attack
stack trace and .odt
Comment 1 aziem 2008-04-20 19:45:58 UTC
Created attachment 53049 [details]
crashes DEV300_m9 but not OOo 2.4.0
Comment 2 aziem 2008-04-20 19:47:22 UTC
Created attachment 53050 [details]
stack trace
Comment 3 eric.savary 2008-04-22 11:07:31 UTC
Sent crash report with summary "i88499"
Regression. Didn't crash in 2.4
Comment 4 bjoern.michaelsen 2008-05-21 17:22:49 UTC
nukes on DEV300 m13 at 0xada97107 in SwXTextField::attachToRange
(this=0xac510e3c, xTextRange=@0xbfacf1b0) at

pDateTime is NULL
Comment 5 bjoern.michaelsen 2008-05-22 12:28:41 UTC
fixed in cws bmichaelsen30bf01, file sw/source/core/unocore/unofield.cxx
Comment 6 max.odendahl 2008-05-22 14:35:01 UTC
duplicate of 88347, already fixed in notes4, which is currently in QA
Comment 7 bjoern.michaelsen 2008-07-04 08:59:42 UTC
removing task and fix from cws bmichaelsen30bf01 as it gets merged into another
cws, fix was already in notes4 which is integrated and document opens fine with
Comment 8 Raphael Bircher 2010-02-08 23:21:39 UTC
Tested with OOo 3.2.0 on Mac OS X 10.5.x, seems to be all ok, so set issue
directly to closed