Re: problem with sablevm-1.1.9 xscale

> So there really is a problem.
> 
> The best next step you can take is to recompile with
> --enable-debugging-features.  This will enable all assert()ions and
> chances are that one of them will fail before the segfault thus possibly
> giving out some better clue as to what the actual problem might be.
> 
> And even if not, then you still want to debug a version of SableVM
> compiled with -O0 (no optimizations) which is the case only when using
> --enable-debugging-features.
> 
> HTH,
> 
> 			Grzegorz B. Prokopski


A) When configured  like this:

./configure --build=i686-linux --host=arm-linux --target=arm-linux   --enable-
real-life-brokenness --with-threading=direct --disable-signals-for-exceptions --
enable-debugging-features


1. It does not seem to find classes in jar file 

/usr/local/bin/sablevm -c RXTXcomm.jar:. CommCheck
java.lang.IllegalArgumentException
   at gnu.java.nio.channels.FileChannelImpl.position (FileChannelImpl.java:401)
   at java.io.RandomAccessFile.skipBytes (RandomAccessFile.java:751)
   at java.util.zip.ZipFile.readEntries (ZipFile.java:230)
   at java.util.zip.ZipFile.getEntries (ZipFile.java:342)
   at java.util.zip.ZipFile.getEntry (ZipFile.java:359)
   at java.util.jar.JarFile.getEntry (JarFile.java:392)
   at java.util.jar.JarFile.getJarEntry (JarFile.java:482)
   at java.net.URLClassLoader$JarURLLoader.getResource (URLClassLoader.java:320)

   at java.net.URLClassLoader.findURLResource (URLClassLoader.java:860)
   at java.net.URLClassLoader.findClass (URLClassLoader.java:746)
   at java.lang.ClassLoader.loadClass (ClassLoader.java:359)
   at java.lang.ClassLoader$1.loadClass (ClassLoader.java:1282)
   at java.lang.ClassLoader.loadClass (ClassLoader.java:303)
   at java.lang.VirtualMachine.main (VirtualMachine.java:99)

so i  unjarred it in /usr/local/share/sablevm-classpath... and it is able to 
run and identify the serial ports!!

but it has problem in SimpleWrite-ing and SimpleRead-ing ....   does not 
read/write properly.



AND

2. No more "brokenness" problem ;). Most(9/10) of the time fails to launch 
graphics/GUI applications.

/usr/local/bin/sablevm   drawingLines

sablevm: thread.c:635: _svmf_resuming_java: Assertion `status == 3 || status ==
4' failed.
Aborted

SableVM version 1.1.9
- compile date and time: 2005-02-16 17:07:43 UTC
- gcc version: 3.3.1
- 'real life brokenness' features enabled
- debugging checks enabled
- copying garbage collection
- bidirectional object layout
- direct-threaded interpreter

B)
3.When  ./configure --build=i686-linux --host=arm-linux --target=arm-linux   --
enable-real-life-brokenness --with-threading=direct --disable-signals-for-
exceptions

It reads the jar file!!
Devel Library
=========================================
Native lib Version = RXTX-2.1-7pre17
Java lib Version   = RXTX-2.1-7pre17
Segmentation fault

gives segmentation faults for RXTX and "brokenness" error for other graphics 
applications

C)
4.When  ./configure --build=i686-linux --host=arm-linux --target=arm-linux   --
enable-real-life-brokenness --with-threading=direct 

reads the jar file hangs for RXTX and "brokenness" error for other graphics 
applications


Please help me find a way to run both rxtx and graphics using one build of 
sablevm :)


cheers

asutosh