Re: compiler errors in Classpath

W liście z śro, 22-09-2004, godz. 16:45, Dayong Gu pisze: 
> ===========================================================
> when use jikes ( jikes-1.21), I got many warnings like:

We all get tons of warnings, especially with newer jikes.  As long as
there's no *errors* - it's all fine.  Are you getting errors?
If yes - can you put up sablevm-classpath compilation log somewhere
so that we could look at it?
 
> and finally, when try to run sablevm, it will fail on
> a "segementation fault" . 

So have you managed to successfuly build sablevm-classpath-1.1.6 or not?

If yes, and if the sablevm actually segfaults, try ./configure with
"--enable-debugging-features" and "--disable-signals-for-exceptions". 
Maybe you will get a failed assertion?

It is also possible that your hardware-monitoring JNI library expects
some different behaviour of SableVM or Classpath classes and it actually
segfaults because of that?

You might get some more clues by running "strace" on sablevm while
executing your program. (you should put up the log on web somewhere
if you want us to look at it).

Hope this helps,

			Grzegorz B. Prokopski

PS: This isn't really development-related question.  Please move
the discussion to sablevm-user.

-- 
Grzegorz B. Prokopski      <[email protected]>
Debian GNU/Linux           http://www.debian.org
SableVM - LGPL'ed Java VM  http://www.sablevm.org
Why SableVM ?!?            http://devel.sablevm.org/wiki/Features