Re: SableVM SDK release and CP 0.15 merge (help needed)
Marcel Wiesweg <[email protected]> Sun, 15 May 2005 17:19:41 +0200
| Newsgroups | gmane.comp.java.vm.sablevm.devel |
|---|---|
| Message-ID | <[email protected]> |
> 2. It makes little sense to make a release with old class library, so > I merged GNU Classpath 0.15, but it did not quite work after the merge. > On any program I try I keep getting something like: > > $ /tmp/usr-sdk/bin/sablevm -Y Sleep > java.lang.Class > at java.security.AllPermission$AllPermissionCollection.add > (AllPermission.java:171) > at java.security.Permissions.add (Permissions.java:126) > at java.net.URLClassLoader.getPermissions (URLClassLoader.java:1104) > at java.security.SecureClassLoader.defineClass > (SecureClassLoader.java:96) > at java.net.URLClassLoader.findClass (URLClassLoader.java:926) > at java.lang.ClassLoader.loadClass (ClassLoader.java:353) > at java.lang.ClassLoader$1.loadClass (ClassLoader.java:1284) > at java.lang.ClassLoader.loadClass (ClassLoader.java:304) > at java.lang.VirtualMachine.main (VirtualMachine.java:99) I had time to get a quick look at this, no solution yet, but what I found out is that the problem is not related to the classes displayed in the backtrace. It is rather java.lang.Object.getClass() which is broken somewhere: it always returns java.lang.Class as the object`s class (see first line in backtrace: it actually is an IllegalArgumentException). This already happens at the stack frame in the beginning of the backtrace, this is only the first time where it results in an error. No time today to look into this any further. Marcel > > With the new repository layout I was able to create shared merge > branches, so to obtain it you can simply do: > > svn co $SVN/sablevm/branches/merge-cp-0.15 svm-merge > svn co $SVN/sablevm-classpath/branches/merge-cp-0.15 svm-cp-merge > > (where $SVN is svn://svn.sablevm.org/ if you don't have write access > to the repository. Otherwise you'll know what $SVN is in your case.) > > > Patches, ideas and any other help with this issue will be greatly > appreciated. The sooner it is resolved, the sooner we can release > SableVM SDK. And as a bonus, if *you* solve it I promise to add yet > another useful module to the first release of SableVM SDK :-) > > Cheers, > > Grzegorz B. Prokopski