Apache OpenOffice (AOO) Bugzilla – Issue 59013
crash in OOo 2.0 spellchecker
Last modified: 2013-02-24 20:43:16 UTC
I don't know if it is still relevant since OOo 2.0.2 should switch to Hun-Spell. But anyway here is the stack from the crashreport: This task has been generated from a crash report. The report can be seen at http://so-web.germany.sun.com/ReportMail/view.ShowCrashReportList?StackId=274731 You may use the command 'crashdebug -id 798833' to get more detailed information on the bug cause. Other ids for use with the 'crashdebug' tool may be found in the HTML frontend via the above URL. ChildEBP RetAddr 00e1f210 62515baa spell680mi!SuggestMgr::ngram(int n = 3, char* s1 = 00e1f2f0 "briquetagem", char* s2 = 00004000 "", int uselen = 1)+0x26 [o:\src680\src.m2\lingucomponent\source\spellcheck\myspell\suggestmgr.cxx @ 510] 00e1f2d0 62514e28 spell680mi!SuggestMgr::ngsuggest(char** wlst = 092178c0 , char* word = 00e1f2f0 "briquetagem", HashMgr* pHMgr = 04dfb078 )+0x69 [o:\src680\src.m2\lingucomponent\source\spellcheck\myspell\suggestmgr.cxx @ 388] 00e1f3c8 62512ee8 spell680mi!MySpell::suggest(char*** slst = 00e1f424 , char* word = 00000000 "")+0x20f [o:\src680\src.m2\lingucomponent\source\spellcheck\myspell\myspell.cxx @ 269] 00e1f434 62513166 spell680mi!SpellChecker::GetProposals(rtl::OUString* rWord = 00e1f51c , com::sun::star::lang::Locale* rLocale = 00e1f4b4 )+0x13e [o:\src680\src.m2\lingucomponent\source\spellcheck\spell\sspellimp.cxx @ 461] 00e1f47c 64464cef spell680mi!SpellChecker::spell(rtl::OUString* rWord = 00e1f51c , com::sun::star::lang::Locale* rLocale = 00e1f4b4 , com::sun::star::uno::Sequence<com::sun::star::beans::PropertyValue>* rProperties = 00e1f67c )+0xc0 [o:\src680\src.m2\lingucomponent\source\spellcheck\spell\sspellimp.cxx @ 516] There are 7 reports for this stack.
Is this a duplicate of Issue 59015? Regards, Andrew
Looks that way. *** This issue has been marked as a duplicate of 59015 ***
The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html
As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew