I've just upgraded to a current 1.5ZC (from a couple of days ago) from a 1.5ZA 
from early march on i386 and am now seeing problems with jdb from the 
sun-jdk-1.3.1.0.1 package.

With the 1.5ZA system running jdb with no arguments produces:

	Initializing jdb...
	> 

and waits for input from the terminal as you would expect.  With 1.5ZC I get:

	Initializing jdb...
	> Internal exception:  java.io.IOException: Invalid argument
	        at java.io.FileInputStream.available(Native Method)
	        at java.io.BufferedInputStream.read(BufferedInputStream.java:282)
	        at java.io.FilterInputStream.read(FilterInputStream.java:93)
	        at java.io.InputStreamReader.fill(InputStreamReader.java:173)
	        at java.io.InputStreamReader.read(InputStreamReader.java:249)
	        at java.io.BufferedReader.fill(BufferedReader.java:139)
	        at java.io.BufferedReader.readLine(BufferedReader.java:299)
	        at java.io.BufferedReader.readLine(BufferedReader.java:362)
	        at com.sun.tools.example.debug.tty.TTY.<init>(TTY.java:611)
	        at com.sun.tools.example.debug.tty.TTY.main(TTY.java:924)


In both cases this with the sun-jdk-1.3.1.0.1 and suse 6.4 packages and with
/emul/linux/dev/dsp symlinked to /dev/sound.  Why mention the last bit?
Here is the really odd bit - If you have some other process (such as artsd) 
open /dev/sound so that jdb *fails* to open /emul/linux/dev/dsp then jdb works 
(doesn't get the io exception) in the 1.5ZC case.

I believe there are other java oddities happening but the above is easily 
reproduced.

I've updated the 1.5ZC kernel to include the linux compatibility changes from
the last couple of days and it makes no difference to the above.

suggestions?

cheers
mark