I've tried that. Upgrading to jdk117_v3 does not fix this. This was apparently caused by a kernel fix that went in from redhat6.0 to redhat6.1 The jdk117_v1a should work without a problem on redhat6.1 and I have'nt had an issue with it so far except this one. Have you ? - Ruchir From: Riyad Kalla <[EMAIL PROTECTED]> To: Ruchir Tewari <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Java, threads, and RedHat 6.1, JNI_CreateVM coredump. Date: Thu, 25 Nov 1999 17:19:52 -0700 Correct me if I'm wrong, but wasn't jdk117_v1a compiled with Glibc2.0 in mind while RH 6.1 is a Glibc2.1 system? Try jdk117_v3 glibc2.1 -Riyad Ruchir Tewari wrote: > JNI_CreateVM does not work on redhat 6.1 when using jdk117_v1a. > Take a look at the following bug report. > http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=6056 > > It says it works with the IBM jdk. > But I've found the IBM jdk to be even less stable than > the blackdown version. > > I've entered a bug at the Blackdown Jitterbug. (Bug # 1526) > > This is quite critical so I hope it gets resolved soon. > > From: Tom Otvos <[EMAIL PROTECTED]> > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > Subject: Java, threads, and RedHat 6.1 > Date: Tue, 23 Nov 1999 17:43:26 -0500 > > I am trying to create a (p)threaded application on Red Hat 6.1 that uses the > Invocation API. Unfortunately, things are not going so well. > > At first, I downloaded the Blackdown 1.2 pre-v2 distribution, but found I > could not link because of glibc incompatibilities as Red Hat 6.1 ships with > glibc 2.1.2. Then, I switched over to the 1.1.7 distribution, including the > native threads updates, which I can successfully build with but when I try > to call JNI_CreateJavaVM, I get a segmentation fault. The stack crawl looks > something like: > > in JNI_CreateJavaVM at jni.c:3924 > in sysInitializeJavaVM at javai.c:832 > in InitializeClassThread at threadruntime.c:111 > in sun_misc_VM_unsuspendSomeThreads at threads.c:87 > in sysThreadInitializeSystemThreads at threads_md.c:140 > in InitializeFinalizerThread at finalize.c:303 > in execute_java_constructor at interpreter.c:153 > in EE from libjava.so > > I am going to try to backtrack and get a reduced case scenario, but I am > afraid I don't know enough about Linux or the internals of the Java VM to > make real progress. So, I have a couple of questions. > > 1) Am I correct in that I cannot use the current Blackdown 1.2 on Red Hat > 6.1? > 2) Since my application is (p)threaded, am I correct that I need a > native-thread version of the Java VM? > 3) Can I use the Invocation API with version 1.1.7 of the Blackdown VM and > native threads? > > I should mention that I have the same application running correctly on > Win32, so I believe that I am using the Invocation API correctly. In > particular, I know about attaching threads and so on. In this case, > however, I am not even getting that far. > > If anyone can shed some light on this, I would be very grateful. > > Tom Otvos > Director of Research, Pervasive Software Inc. > > "Don't think you are. Know you are." - Morpheus > > ---------------------------------------------------------------------- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > > ---------------------------------------------------------------------- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- [ Riyad Kalla ] [ [EMAIL PROTECTED] ] [ CS - Major ] [ University of Arizona ] ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
