Issue 4435 - Core-Dump when using Thesaurus
Summary: Core-Dump when using Thesaurus
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: khendricks
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-03 12:22 UTC by Unknown
Modified: 2003-09-08 16:56 UTC (History)
3 users (show)

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


Attachments
Image of the Thesaurus window when crashing (120.73 KB, image/jpeg)
2002-05-03 12:24 UTC, Unknown
no flags Details
Backtrace-file from GDB (7.50 KB, text/plain)
2002-05-14 09:20 UTC, Unknown
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-05-03 12:22:45 UTC
I'm using the german version of OO and have the german dictionary installed. The
german dictionary is the default one.

I get a reproducible core dump with this scenario:

1) Start OpenOffice
2) Type a wrong word in english: buiding
3) Press F7 to call spell checker
4) Change language from Deutsch to English
5) Press Thesaurus-button at right corner.
6) OpenOffice core dumps :-(
     The files get saved, so I can recover them :-)
     But OO really stops as soon as I press OK
Comment 1 Unknown 2002-05-03 12:24:07 UTC
Created attachment 1543 [details]
Image of the Thesaurus window when crashing
Comment 2 Unknown 2002-05-03 12:27:04 UTC
Linux 2.4.3-20mdk (Mandrake 8.0 distribution)
--------------8<--------------------
rmalta@cenit4:~ > gcc -v
Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux/2.96/specs
gcc version 2.96 20000731 (Linux-Mandrake 8.0 2.96-0.48mdk)
--------------8<--------------------
rmalta@cenit4:~ > rpm -qi glibc
Name   : glibc                   Relocations: (not relocateable)
Version: 2.2.2                        Vendor: MandrakeSoft
Comment 3 Unknown 2002-05-03 13:10:58 UTC
I've tested it now without the german dictionary. So only english is
installed !!

Same problem: as soon as I press the Thesaurus button OO crashes.

I'm using the german version of OO, so it should be usefull to test
the english version as it could be a single problem of the german
version, isn't so ??
Comment 4 aschrage 2002-05-12 12:51:17 UTC
I have the exact same error when using the Thesaurus. I'm using OO 1.0
(German version) on Windows 98 SE. I'm using the keyboard shortcut
CTRL + F7
Comment 5 khendricks 2002-05-12 17:16:47 UTC
Hi,

This bug is mine (lingucomponent - most probably).

I will try to recreate this under Linux and get back to you.

Thanks for your bug report.

Kevin
Comment 6 khendricks 2002-05-13 19:47:47 UTC
Hi,  
  
I finally found a moment and with the English language linux build I  
simply can not recreate your crashes at all.  It works fine.  
I tried it ten times in a row and each and every one worked. 
 
This bug seems to be lreated to the German builds (independent of 
whether there is a German dictionary installed). 
 
So the only way I will be able to fix this is for you to help me 
track down the bug itself. 
 
Under Linux, please repeat the sequence of steps that generates the 
crash and when the Error dialog starts up please don't hit okay and 
instead grab gdb and use it to attach to the highest numbered 
process running soffice.bin and then run a backtrace on it and 
please send me the results. 
 
If are are unfamiliar with using gdb and attaching to already 
running processes, then simply please try the following: 
 
cd OpenOffice.org1.0 
cd program 
 
then edit the "soffice" shell script here and change the next to the 
last line: 
 
        exec "$sd_prog/$sd_binary" "$1" "$2" "$3" "$4" "$5" "$6" 
"$7" "$8" "$9" 
 
 
to be 
 
        gdb "$sd_prog/$sd_binary" "$1" "$2" "$3" "$4" "$5" "$6" "$7" 
"$8" "$9" 
 
 
Then the next time you start up OpenOffice.org it will instead start 
up gdb properly. 
 
At the gdb prompt just enter "run". 
 
When the segfault happens, control will return to gdb, and then 
simply enter the command "bt" 
 
This will generate the backtrace so that I have some idea of why 
this is happening in the German builds and not the English builds 
(perhaps the builds always assume if a dictionary exists a thesaurus 
exists...). 
 
Thanks, 
 
Kevin 
 
 
 
Comment 7 Unknown 2002-05-14 09:20:01 UTC
Created attachment 1636 [details]
Backtrace-file from GDB
Comment 8 khendricks 2002-05-14 14:06:54 UTC
Hi,

Thanks for the backtrace.  Basically it tells me that the en_US 
Thesaurus was never initialized properly and I think I know why 
and maybe even a small workaround for the problem.

Will you please try the following for me:

cd to whereever you did the main install of openoffice

In my case this would be:

cd /opt/OpenOffice.org1.0

Then do the following:

cd share/wordbook/
ls

# here you should see a directory called english and one called
# german (or some variations along those lines)

Then do the following:

cd english
cp th_en_US* ../german/

That will copy the thesaurus data files to the share/wordbook/
german/ (or whatever the german version calls it .. deutsche?)

Then try restarting OpenOffice.org and rerunning your test.

If the test now passes (it should) then I will need to find a 
language neutral (not english or german) place to store all 
thesaurus data files so that they can be properly found under all 
builds (german and english).

Please give this workaround a try and let me know if it does fix 
the problem.  If so, I will figure out how to fix it in time for the next  
OOo 1.0.X release.

Thanks again for your help tracking this one down.

Kevin

Comment 9 maccy 2002-05-14 15:23:14 UTC
that fixes the thing for me with the German Windoze OO.o 1.0 I have at
the moment. Thanks Kevin!
Comment 10 Unknown 2002-05-15 08:27:51 UTC
Hi Kevin,

you fixed the problem :-))

I've copied the thesaurus files from the english directory into the
german(it is really called so :-) directory.

Now when I change the language I get the thesaurus window and no seg
fault :-)

Thanks :-)
Comment 11 khendricks 2002-05-26 03:26:46 UTC
 Hi, 
 
Fix to this problem commited to OOO_STABLE_1 and will be on OOo 
1.0.1 
 
So closing as fixed. 
 
Thanks, 
 
Kevin 
Comment 12 khendricks 2002-10-31 19:09:54 UTC
closing