Apache OpenOffice (AOO) Bugzilla – Issue 77098
crash in lingucomponent spell checker
Last modified: 2013-02-24 20:43:17 UTC
This issues is from the crash report tool. There are already 330(!) reports with this stack. The version where this happened is OOF680m11 and OOE680. The stack looks like this: spell680mi!SuggestMgr::replchars(char** wlst = 0914aaf0 , char* word = 00ffef14 "Requirements", int ns = 0, int cpdsuggest = 0)+0x66 [o:\oof680\src.m11\lingucomponent\source\spellcheck\hunspell\suggestmgr.cxx @ 379] spell680mi!SuggestMgr::suggest(char*** slst = 00fff384 , char* w = 00000000 "", int nsug = 0)+0xd3 [o:\oof680\src.m11\lingucomponent\source\spellcheck\hunspell\suggestmgr.cxx @ 148] spell680mi!Hunspell::suggest(char*** slst = 00fff384 , char* word = 0550def0 "")+0x427 [o:\oof680\src.m11\lingucomponent\source\spellcheck\hunspell\hunspell.cxx @ 674] spell680mi!SpellChecker::GetProposals(rtl::OUString* rWord = 00fff480 , com::sun::star::lang::Locale* rLocale = 00fff414 )+0x13e [o:\oof680\src.m11\lingucomponent\source\spellcheck\spell\sspellimp.cxx @ 495] spell680mi!SpellChecker::spell(rtl::OUString* rWord = 00fff480 , com::sun::star::lang::Locale* rLocale = 00fff414 , com::sun::star::uno::Sequence<com::sun::star::beans::PropertyValue>* rProperties = 00fff624 )+0xc0 [o:\oof680\src.m11\lingucomponent\source\spellcheck\spell\sspellimp.cxx @ 550] lng680mi!SpellCheckerDispatcher::spell_Impl(rtl::OUString* rWord = 01eb03a8 , short nLanguage = 0x809, com::sun::star::uno::Sequence<com::sun::star::beans::PropertyValue>* rProperties = 00fff624 , unsigned char bCheckDics = 0x1 '')+0x24d [o:\oof680\src.m11\linguistic\source\spelldsp.cxx @ 713]
Maybe this is a problem with the new Hunspell 1.5 integrated(???) in Novell versions of OpenOffice.org OR a problem with the new en_GB dictionary (see Issue 76100). I will fix in CWS hunspell2 some real bugs: http://sourceforge.net/tracker/index.php?func=detail&aid=1698240&group_id=143754&atid=756395 http://sourceforge.net/tracker/index.php?func=detail&aid=1693875&group_id=143754&atid=756395 (first bug is only problem for OpenOffice.org)
That can easily be. That's up to you to decide when you look up the code. Still even if the cause was the broken dictionary the office should not crash. If that can be done you have two choice - disable the broken dictionary or - run with whatever you mentioned to successfully obtain from it Since lingucomponent can hardly report errors in the UI (after all it can be called via the API only) I think disabling would be a good choice in that case one does at least know that something went wrong. The other way it remains unclear what works and what not. But the choice is left up to you. In any way I have confirmed that there should never be error messages printed to stderr or stdout. Ideally there should be an appropriate exception to report such a problem, but that is unfortunately missing and a RuntimeException should not be misused this way.
corrupt REP definition in new en_GB.aff *** This issue has been marked as a duplicate of 76100 ***
close the duplicate