> -----Original Message----- > From: Dan Gould [mailto:[EMAIL PROTECTED] > An unexpected exception has been detected in native code outside the VM. > Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at > PC=0x7C9 > 2AE22 > Function=RtlImpersonateSelf+0x3A5 > Library=C:\WINDOWS\system32\ntdll.dll > > Current Java thread: > at java.util.zip.ZipFile.getNextEntry(Native Method) > at java.util.zip.ZipFile.access$400(ZipFile.java:26) > at java.util.zip.ZipFile$2.nextElement(ZipFile.java:312) > - locked <0x104f82a0> (a java.util.jar.JarFile) > at java.util.jar.JarFile$1.nextElement(JarFile.java:211) > at > sun.misc.URLClassPath$JarLoader.validIndex(URLClassPath.java:642)
This is caused by something strange in the JVM when an attempt is made to update a jar file which is currently on the stack. Basically if the 'ant setup' command is invoked and the downloaded magic install is more recent, then everything goes according to plan. The good thing to know is that independently of the above error report - the setup procedure did actually work and magic is installed on your system. Basically we need to get in place a non-ant based install procedure for Magic. Niclas has already started some thing s in this area (i.e. the above is a temporary but non-fatal issue). Cheers, Steve. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
