Re: JDK 1.4 port status
Jim Hazen <[EMAIL PROTECTED]> writes: > Back at the end of August it was said that a first Blackdown release > (beta) of JDK 1.4 would happen in two weeks. It's been a bit longer > than that. Anyone know what's going on? New features (generics, > etc) being crammed into 1.4 before the release? Any idea when we'll > see a Blackdown beta? FCS? We are near a first beta release. (We'll make a least one beta release before doing some release candidates.) Juergen -- Juergen Kreileder, Blackdown Java-Linux Team http://www.blackdown.org/java-linux.html Run Java 2 SE v1.3.1 on your iPAQ: http://www.handhelds.org/pipermail/ipaq/2001-June/007221.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problems with "java" executable
Hi, I just starting to use Blackdown's JDK for Linux, version 1.3.1. I have a Linux RedHat 7.0 computer with all the latest libc libraries installed. My problem is this: when I first run the java executable, like "java -version", the output is this: java version "1.3.1" Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.3.1-FCS) Java HotSpot(TM) Client VM (build Blackdown-1.3.1-FCS, mixed mode) After that, anytime I run it I get this output: java version "1.3.1" Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.3.1-FCS) Java HotSpot(TM) Client VM (build Blackdown-1.3.1-FCS, mixed mode) Another exception has been detected while we were handling last error. Dumping information about last error: ERROR REPORT FILE = (N/A) PC= 0x0x40269988 SIGNAL= 11 FUNCTION NAME = (N/A) LIBRARY NAME = (N/A) Please check ERROR REPORT FILE for further information, if there is any. Good bye. Segmentation fault Aparently java ran fine, but it always ends with that message. Is this a bug? How do I fix it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RedHat 7.2/JDK compatibility?
Has anyone tried the latest JDKs (Blackdown/Sun/IBM) with RedHat 7.2? In previous RedHat upgrades I had discovered incompatibilities with the Java JDKs. In one case I had to downgrade (painful!). Thanks, Alexander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems with "java" executable
Yes, I know... RedHat 7.0 is kind of old now... but my glibc is the latest for redhat 7.0 as far as I know... the version is 2.2.4-18.7.0 It's a strange thing: when running classes, like "java HelloWorld", the problem does NOT occur... the class is executing perfectly... On Tuesday 23 October 2001 11:22 am, Cynthia Jeness wrote: > Alexander, > > With RedHat 7.0, there were some mandatory patches available on the RedHat > site which were required to successfully run Java. It has been awhile, but > I think that they were related to glibc. Did you apply these patches? > > Cynthia Jeness > > Alexandre Saur wrote: > > Hi, > >I just starting to use Blackdown's JDK for Linux, version 1.3.1. > >I have a Linux RedHat 7.0 computer with all the latest libc libraries > > installed. > >My problem is this: when I first run the java executable, like "java > > -version", the output is this: > > > > java version "1.3.1" > > Java(TM) 2 Runtime Environment, Standard Edition (build > > Blackdown-1.3.1-FCS) Java HotSpot(TM) Client VM (build > > Blackdown-1.3.1-FCS, mixed mode) > > > > After that, anytime I run it I get this output: > > > > java version "1.3.1" > > Java(TM) 2 Runtime Environment, Standard Edition (build > > Blackdown-1.3.1-FCS) Java HotSpot(TM) Client VM (build > > Blackdown-1.3.1-FCS, mixed mode) > > > > > > > > Another exception has been detected while we were handling last error. > > Dumping information about last error: > > ERROR REPORT FILE = (N/A) > > PC= 0x0x40269988 > > SIGNAL= 11 > > FUNCTION NAME = (N/A) > > LIBRARY NAME = (N/A) > > Please check ERROR REPORT FILE for further information, if there is any. > > Good bye. > > Segmentation fault > > > >Aparently java ran fine, but it always ends with that message. Is this > > a bug? How do I fix it? > > > > -- > > 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]
RE: RedHat 7.2/JDK compatibility?
All, Redhat 7.2 comes with the default linux kernel of 2.4.3. Please be careful with this kernel. Many JDK's(esp 1.3.x) were not qualified for this linux kernel. Linux kernel has gone many changes especially in Thread scheduling algos which need to be qualified by JDK developers. If not you might face the same problem what I'm facing. IBM jdk - 1.3.1 in 2.4.3 kernel leaks and unstable. Sun is far better. I didn't try with blackdown. These are for info and nothing to be inferred from. Seeing is believing Reg Ved -Original Message- From: Alexander V. Konstantinou [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2001 7:04 AM To: [EMAIL PROTECTED] Subject: RedHat 7.2/JDK compatibility? Has anyone tried the latest JDKs (Blackdown/Sun/IBM) with RedHat 7.2? In previous RedHat upgrades I had discovered incompatibilities with the Java JDKs. In one case I had to downgrade (painful!). Thanks, Alexander -- 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]
Re: Problems with "java" executable
It could be http://developer.java.sun.com/developer/bugParade/bugs/4422213.html which is a generic hotspot bug but was found on linux :*( regards calvin Alexandre Saur wrote: > > Yes, I know... RedHat 7.0 is kind of old now... > but my glibc is the latest for redhat 7.0 as far as I know... the version is > 2.2.4-18.7.0 > It's a strange thing: when running classes, like "java HelloWorld", the > problem does NOT occur... the class is executing perfectly... > > On Tuesday 23 October 2001 11:22 am, Cynthia Jeness wrote: > > Alexander, > > > > With RedHat 7.0, there were some mandatory patches available on the RedHat > > site which were required to successfully run Java. It has been awhile, but > > I think that they were related to glibc. Did you apply these patches? > > > > Cynthia Jeness > > > > Alexandre Saur wrote: > > > Hi, > > >I just starting to use Blackdown's JDK for Linux, version 1.3.1. > > >I have a Linux RedHat 7.0 computer with all the latest libc libraries > > > installed. > > >My problem is this: when I first run the java executable, like "java > > > -version", the output is this: > > > > > > java version "1.3.1" > > > Java(TM) 2 Runtime Environment, Standard Edition (build > > > Blackdown-1.3.1-FCS) Java HotSpot(TM) Client VM (build > > > Blackdown-1.3.1-FCS, mixed mode) > > > > > > After that, anytime I run it I get this output: > > > > > > java version "1.3.1" > > > Java(TM) 2 Runtime Environment, Standard Edition (build > > > Blackdown-1.3.1-FCS) Java HotSpot(TM) Client VM (build > > > Blackdown-1.3.1-FCS, mixed mode) > > > > > > > > > > > > Another exception has been detected while we were handling last error. > > > Dumping information about last error: > > > ERROR REPORT FILE = (N/A) > > > PC= 0x0x40269988 > > > SIGNAL= 11 > > > FUNCTION NAME = (N/A) > > > LIBRARY NAME = (N/A) > > > Please check ERROR REPORT FILE for further information, if there is any. > > > Good bye. > > > Segmentation fault > > > > > >Aparently java ran fine, but it always ends with that message. Is this > > > a bug? How do I fix it? > > > > > > -- > > > 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] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: JDK 1.4 port status
Sounds great. Blackdown rocks. -Jim > Jim Hazen <[EMAIL PROTECTED]> writes: > > > Back at the end of August it was said that a first Blackdown release > > (beta) of JDK 1.4 would happen in two weeks. It's been a bit longer > > than that. Anyone know what's going on? New features (generics, > > etc) being crammed into 1.4 before the release? Any idea when we'll > > see a Blackdown beta? FCS? > > We are near a first beta release. (We'll make a least one beta > release before doing some release candidates.) > > Juergen > > -- > Juergen Kreileder, Blackdown Java-Linux Team > http://www.blackdown.org/java-linux.html > Run Java 2 SE v1.3.1 on your iPAQ: > http://www.handhelds.org/pipermail/ipaq/2001-June/007221.html > > -- > 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]
subscribe
__ === ÐÂÀËÃâ·Ñµç×ÓÓÊÏä (http://mail.sina.com.cn) ÐÂÀË·ÖÀàÐÅÏ¢££³ÇÊÐÉú»îÖ¸ÄÏ£¡ (http://classad.sina.com.cn/) ÊÀ½ç±¡¢¼×A¡¢Å·ÖÞÁªÈü¡¶©×ãÇò¶ÌÐÅ£¬Ó®ÊÖ»ú´ó½±£¡ (http://sms.sina.com.cn/sport.html) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
