I also noticed that upon upgrading to glibc-2.1.2 (which is required by RC3) and
installing RC3. The jdk1.1.8 from ibm would give a SIGSEGV when trying to open
Socket to an non-existence host.

For example,

Socket sock = new Socket ("somehost", someport)

would give a core dump if "somehost" does not exists.

Is this a glibc problem? Has anybody encountered this as well?

thanks,
Andy

[EMAIL PROTECTED] wrote:

>
>         Hello Java-Linux people
>
>     I have installed the Blackdown's 1.2 a couple of weeks ago;I also have IBM's
> 1.1.8     it is strange that the behaviour of some programs changed;and I don't
>    mean the changes brought by the 1.2 API or implemetation differences;
>         The programs run differently on IBM118 now,compared to when
>   1.2 was not installed!        Does 1.2 influence the behaviour of other VM-s
>  on the system?(besides the CLASSPATH which I set according to the JDK
>  I use);
>         I will be more specific:
>
>         I used a BufferedInputStream(System.in,1) to be able to sense individual
> keypresses instead of having to wait for Return.And it worked fine with IBM118;
> Later when I installed 1.2rc3 and tried it and did't work.I tried running it
> again on 118 (assuming that BufferedInputStream is implemented slightly
> differently on 1.2) but it no longer run as it was supposed to even with the
> same CLASSPATH as initially;
>
>         Do other env. variables have something to do with it?Or it is not only
> related 1.2 JDK's;
>
>    Some friends said that a new 1.2 installation also modified Netscape's
> VM  behaviour.
>
>         Thanks in advance.
>
>         By the way : 1000 thanks to all of you  involved in any way in porting
>            Java to Linux.
>
>
>
>
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to