[Bug 128] Loading .jar files created by jar fails

[email protected] Thu, 14 Apr 2005 21:59:35 -0400
Newsgroups gmane.comp.java.vm.sablevm.bugs
Message-ID <[email protected]>
http://sablevm.org/bugs/show_bug.cgi?id=128

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|[email protected]    |[email protected]



------- Additional Comments From [email protected]  2005-04-14 21:59 -------
I think it's a bug fixed right after 1.11.3 release.  I thought it got in.

Can you please try doing the following change and retrying:

Index: sablevm/trunk/src/libsablevm/zip_file_reader.c
===================================================================
--- sablevm/trunk/src/libsablevm/zip_file_reader.c      (revision 3823)
+++ sablevm/trunk/src/libsablevm/zip_file_reader.c      (revision 3824)
@@ -139,7 +139,7 @@
   if (_svmm_gzalloc_zip_file (env, zip_file) != JNI_OK)
     goto error;

-  if (_svmm_gmalloc_cchars (env, strlen (file_name), zip_file->name) !=
+  if (_svmm_gmalloc_cchars (env, strlen (file_name) + 1, zip_file->name) !=
       JNI_OK)
     goto error;
   strcpy (zip_file->name, file_name);

I tried with Debian's 1.11.3 which contains the above fix and:

gadek@gadek:/tmp$ sablevm -Yc testme.jar de.vdr.ApplicationManager
java.lang.UnsatisfiedLinkError: Native library `vdrmhp' not found (as file
`libvdrmhp') in gnu.classpath.boot.library.path and java.library.path
   at java.lang.Runtime.loadLibrary (Runtime.java:780)
   at java.lang.System.loadLibrary (System.java:518)
   at de.vdr.ApplicationManager.static{} (ApplicationManager.java:19)
   at java.lang.VMClass.step8 (VMClass.java)
   at java.lang.Class.initialize (Class.java:147)
   at java.lang.VirtualMachine.invokeMain (VirtualMachine.java)
   at java.lang.VirtualMachine.main (VirtualMachine.java:108)




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.