Re: SableVM on ARM Zaurus

> > After the stack trace is shown, the bottom lines says "...1 more". I
> > have to admit that I don't know how the rest of the stack trace can be
> > displayed, so I exit forcively by pressing Ctrl-C. I guess that's why
> > you see the "killed by SIGINT" message.
> 
> Hmm... so it hangs?!

I really don't know. I guessed that "...3 more" means I have to press
some key-combination to continue. I just don't know the combination,
so I exit with Ctrl-C
 
> add --disable-errors-on-warnings to configure options you use,
> and include the output of 'sablevm -V' in yoru next email, just so
> that we were sure you got all the options right.

sablevm -V shows:
SableVM version 1.1.8
- compile date and time: 2005-01-08 20:11:46 UTC
- gcc version: 3.3.2
- real life brokeness' features enabled
- debugging checks enabled
- copying garbage collection
- bidirectional object layout
- switch threaded interpreter

The app I try to run is:

import java.awt.*;

public class Test
{
  public static void main(String[] args)
  {
    Frame f = new Frame("Java on Zaurus");
    Dimension d = Toolkit.getDefaultToolkit().getScreenSize();
    System.out.println("Screen size: " + d);
  }
}

> Do you get any additional information (ie. a failed assertion) when
> ran normally?

Nope, no additional errors, just the "Unsatisfied link error"

> I do not know if you have gdb running reliably on your Taurus
> (I remember there were problems with it sometimes), so if I were
> you, I'd put in the above function a few 'printf(); fflush(NULL);'
> statments that would show with what parameters its called,
> what is the control flow inside and where exactly it fails!

I will try to see how that works out.