javac throwing native exception

Thread view:

anusrik - 27 Apr 2006 06:08 GMT

Hi,
I am getting this error when javac is run on JDK1.3.1
An unexpected exception has been detected in native code outside the
VM.Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at
PC=0x6d3c794e
Function name=ZIP_Open
Library=c:\jdk1.3.1\jre\bin\zip.dll
Current Java thread:
at java.util.zip.ZipFile.getNextEntry(Native Method)
at java.util.zip.ZipFile.access$300(ZipFile.java:29)
at java.util.zip.ZipFile$2.nextElement(ZipFile.java:295)

Can someone please help. It used to compile earlier and now suddenly
has started failing.

Thanks,
Anu

Reply to this Message

Tony Morris - 27 Apr 2006 06:49 GMT

> Hi,
> I am getting this error when javac is run on JDK1.3.1
[quoted text clipped - 13 lines]
> Thanks,
> Anu

This is a bug in the JVM implementation.
Are you using the IBM implementation (*internal chuckle*)?
Try updating to the latest version.

Signature

Tony Morris
http://tmorris.net/

Reply to this Message

anusrik - 09 May 2006 13:07 GMT

The issue is it used to compile fine for long time and suddenly this
has surfaced. if it was a bug then it shouldn't have compiled earlier
Also another fact is that there are lots of javac targets in my build
file and only one particular one has started failing regularly now. So
why are the others not failing if its a bug.
when does this bug surface?

Thanks,
Anu

Reply to this Message

Fred Kleinschmidt - 09 May 2006 15:47 GMT

> The issue is it used to compile fine for long time and suddenly this
> has surfaced. if it was a bug then it shouldn't have compiled earlier
[quoted text clipped - 5 lines]
> Thanks,
> Anu

It's because you have too many semicolons between the end of line 42
and the beginning of line 43

Reply to this Message

Chris Uppal - 09 May 2006 17:30 GMT

> The issue is it used to compile fine for long time and suddenly this
> has surfaced. if it was a bug then it shouldn't have compiled earlier
> Also another fact is that there are lots of javac targets in my build
> file and only one particular one has started failing regularly now.

One possibility is that you have a corrupt JAR or ZIP file somewhere on your
system, and which is used by only one of your build targets. You could try to
pin down which JAR/ZIP it is looking in (say, by using a file-access monitoring
tools like Filemon from www.sysinternals.com) and rebuild or replace that.

-- chris

Reply to this Message

javac throwing native exception

Free Magazines