Issue 15958 - javaldx generates segmentation fault on RH 9.0
Summary: javaldx generates segmentation fault on RH 9.0
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Olaf Felka
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-23 17:57 UTC by prgmgr
Modified: 2003-09-08 16:53 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description prgmgr 2003-06-23 17:57:47 UTC 
Javaldx, used for detecting the appropiate LD_LIBRARY_PATH settings, seg faults
on RH 9.0.  This causes OOo to display the "... java install corrupted ..."
error message when OOo tries to run Java.

The workaround is to manually set the appropiate LD_LIBRARY_PATH settings.
Comment 1 Olaf Felka 2003-06-24 09:16:38 UTC 
I can't reproduce on my RH 9 machine. Have you changed any of your
LD_LIBRARY_PATH settings?
Hi Joachim,
any idea what might happen here?
Comment 2 joachim.lingner 2003-06-24 09:25:49 UTC 
We have not made changes to javaldx recently.
Comment 3 prgmgr 2003-06-25 17:49:43 UTC 
LD_LIBRARY_PATH is not set by default in the shell.

I am currently running a stock RH 9.0 workstation configuration.
I'll try applying the RH 9.0 updates that just recently were posted.

Just curious, how are you trying to reproduce the bug?

I am running the javaldx program by hand from the directory

<install dir>/program/

When running the soffice script, the LD_LIBRARY_PATH variable is set to

/opt/OOo/OpenOffice.org1.1Beta2/program/remote:
/opt/OOo/OpenOffice.org1.1Beta2/program


No changes are made after javaldx is run in the script. 
$java_ld_library_path is not set.
Comment 4 joachim.lingner 2003-06-26 09:53:56 UTC 
javaldx prints a couple of path strings to stdout which are then put
into the LD_LIBRARY_PATH by the soffice script. So, running javaldx
does not change the LD_LIBRARY_PATH. 
Do you have selected a Java during setup?
Do you have a <offic>/user/config/javarc?
Does the javarc contains the entries RuntimeLib and JavaLibPath? The
entries could look as the following example but must correspond to
your selected Java.

Home=file:///local/jl/645m4s1/program/j2re1.4.1_02
RuntimeLib=file:///local/jl/645m4s1/program/j2re1.4.1_02/lib/i386/client/libjvm.so
JavaLibPath=/local/jl/645m4s1/program/j2re1.4.1_02/lib/i386/client:/local/jl/645m4s1/program/j2re1.4.1_02/lib/i386/native_threads:/local/jl/645m4s1/program/j2re1.4.1_02/lib/i386


Are you able to provide a callstack?
Comment 5 joachim.lingner 2003-06-26 10:52:36 UTC 
I got the word that
setting 
LD_ASSUME_KERNEL=2.2.5 

on a RH may cure some Java problems. Maybe it's worth a try.
Comment 6 prgmgr 2003-06-26 19:32:54 UTC 
LD_ASSUME_KERNEL=2.2.5 stops javaldx from segfaulting on RH 9.0.

I tested javaldx by hand and running it from the soffice script, and
OOo now can use Java properly.
Comment 7 Olaf Felka 2003-07-02 11:54:57 UTC 
Please help me out now. Is this still a bug? Do we have a workaround?
Or is this issue closeable? (-:
Comment 8 prgmgr 2003-07-02 14:06:24 UTC 
I'm going to mark this as invalid.

If you patch up RH 9.0 with all the latest updates ( my guess is that
either the glibc or kernel update fixed things ), the problem goes away.

There is also the LD_ASSUME_KERNEL workaround.
Comment 9 prgmgr 2003-07-02 14:07:02 UTC 
Updating the OS with the latest patches or using the LD_ASSUME_KERNEL
workaround will resolve this problem.