When the size of the installed path of javaws is more than 59bytes and it includes some double-byte characters on Solaris/Linux Jaws application manager can't be launched and segmentation fault occurs.

This is reproducible with b22 and b23 and not reproducible with b21.
So this is a regression.

4852001's fix was integrated into b22.
After the fix(B21 and b22,) when the jaws's path is less than 59byte and includes double-byte characters, application manager and jnlp application can work, so I can confirm 4852001's fix in this case.
However, a new problem(= this bug) started to occur from b22.

===================================================================
OS/Locale : RH Linux8.0 / ja_JP.eucJP
              Solaris10 b33 Sparc / ja, ja_JP.PCK
              Solairs 9 UR2 x86 /ja, ja_JP.PCK

* This problem is not reproducible on ja_JP.UTF8

The installed path I tried for RH8.0:

[Failed cases]
1)
/home/tokunaga/\u65e5\u672c\u8a9e\u3058\u3047\u30fc\u3064\u30fc\u3042\u30fc\u308b\u3044\u30fc\uff11\uff12\uff13/javaws/javaws
 ==> 60 bytes. It inculdeds 16 double-byte characters

2)
/home/tokunaga/linux/\u65e5\u672c\u8a9e\u3058\u3047\u30fc\u3064\u30fc\u3042\u30fc\u308b\u3044\u30fc/javaws/javaws
 ==> 60 bytes. It inculdeds 13 double-byte characters

3)
/home/tokunaga/linux/rh8.0/\u65e5\u672c\u8a9e\u3058\u3047\u30fc\u3042\u30fc\u308b\u3044/javaws/javaws
 ==> 60 bytes. It inculdeds 10 double-byte characters


[Passed cases]
1)
/home/tokunaga/\u65e5\u672c\u8a9e\u3058\u3047\u30fc\u3064\u30fc\u3042\u30fc\u308b\u3044\u30fc\uff11\uff12/javaws/javaws
 ==> 59 bytes. It includes 15 double-byte characters

2)
/home/tokunaga/b23/\u65e5\u672c\u8a9e\u3058\u3047\u30fc\u3064\u30fc\u3042\u30fc\u308b\u3044\u30fc/javaws/javaws
 ==> 59bytes. It includes 13 double-byte characters

3)
/home/tokunaga/\u65e5\u672c\u8a9e\u3058\u3047\u30fc\u3064\u30fc\u3042\u30fc\u308b\u3044\u30fc\uff11\uff1234/javaws/javaws
 ==> 60 bytes. It includes 15 double-byte characters.
     * The directory's name which includes double-byte characters includes 2 single byte characters. This case is PASSED though the size of the path is 60bytes.

===================================================================

On Windows same kind of phenomenon is seen.

I tried the test on Windows XP professional japanese.

In case of the path below(50 byte), jaws works fine.
G:\Program Files\Java\j2re1.4.2\\u65e5\u672c\u8a9e\bin\javaw.exe

In case of the path below(70 byte), jaws doesn't work;
G:\Program Files\Java\j2re1.4.2\\u65e5\u672c\u8a9e\u30b8\u30a7\u30fc\u30c4\u30fc\u30a2\u30fc\u30eb\u30a4\u30fc\bin\javaw.exe

Installation is done successfully, but Jaws application manager can't be launched and an error dialog shows up saying like below;
  *******************************************************
   Installation is not correct. Error occured in calling Java VM(Sys Exec).
   G:\Program Files\Java\j2re1.4.2\bin\javaws.exe
  *******************************************************
This is the path of javaws.exe which I tried just bofore the problem occured;
Before I installed j2re in Files\Java\j2re1.4.2\\u65e5\u672c\u8a9e\u30b8\u30a7\u30fc\u30c4\u30fc\u30a2\u30fc\u30eb\u30a4\u30fc,
I installed j2re in G:\Program Files\Java\j2re1.4.2 and Jaws application manager worked fine.
So jaws seems to point to the jaws path installed previously.


-----------------------------------------------------------------------------

Regarding Solaris:
I found that this problem occured when the path of javaws was more than 59 byte and then the number of the size was odd number.
When it was a even number, the problem didn't occur.

This phenomenon was seen on both of ja and ja_JP.PCK locale.
The problem was never seen on ja_JP.UTF8 locale.

###@###.### 2003-05-20

-----------------------------------------------------------------------------