This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
Re: NullPointer + Jars
- To: Bryce McKinlay <bryce at albatross dot co dot nz>
- Subject: Re: NullPointer + Jars
- From: "Gregory R. Warnes" <warnes at biostat dot washington dot edu>
- Date: Fri, 19 May 2000 02:11:29 +0000 (GMT)
- cc: gcj Discussion List <java-discuss at sourceware dot cygnus dot com>
On Fri, 19 May 2000, Bryce McKinlay wrote:
BM>> "Gregory R. Warnes" wrote:
BM>>
BM>> > The example program "HelloDate.java" is attached, as is the getopt jar
BM>> > file.
BM>> >
BM>> > 1) My code uses the gnu getopt code for java. When the jar file is in the
BM>> > classpath, the program throws a NullPointerException on startup (see
BM>> > below). When the un-jar-ed data is on the classpath, everything runs
BM>> > correctly.
BM>>
BM>> As you've probably guessed, the interpreter is much less well tested than the rest
BM>> of (lib)gcj. The reason your finding bugs here is possibly because nobody has tried
BM>> to do this before (that is, put a .jar file on the classpath and run something from
BM>> it ;-)
Actually, I didn't want to touch the interpreter, so I the getopt code is
compiled in.
BM>> I haven't tried your test case, but I think I found the problem. Can you try the
BM>> patch below?
Will try..
BM>>
BM>> > libgcj configuration:
BM>> >
BM>> > ../libgcj/configure --prefix=/usr --disable-threads --norecursion
BM>>
BM>> Any particular reason to build without threads? Was there a problem there? Just
BM>> curious...
Yes actually. I have a cluster of machines running MOSIX. MOSIX will
dynamically migrate processes around the cluster in order to get the
maximum performance. Unfortunately, MOSIX doesn't support (kernel)
threaded processes.
-Greg