Re: compiler errors in Classpath
"Dayong Gu" <[email protected]>
| Newsgroups | gmane.comp.java.vm.sablevm.general |
|---|---|
| Message-ID | <007d01c4a5c6$8a298120$928c9d8e@Dayong> |
Hi, Finally, I can make the original version of sablevm1.1.6 run spec jbb to the end on Mandrake 9.0 with a kernel 2.4.19 with patch for performance counters. It turns out that I have to disable some features to let it run. I did not find the reason for it, but I find only when I use disable-debugging-features and disable-signals-for-exceptions and also make symbolic link to library by hand, sablevm can run the Spec jbb to the end. ( But still has some warning about "gtk-peers") For the instructed version ( with PCL) , there is still some problem, sablevm could be terminated in the middle. Thanks for Greg's hints. Cheers, Dayong Sorry for send it to developer mailing list by mistake. ( just a reply to last mail cause it) ----- Original Message ----- From: "Grzegorz B. Prokopski" <[email protected]> To: "SableVM-User" <[email protected]> Cc: "SableVM Developers Mailing List" <[email protected]> Sent: Thursday, September 23, 2004 1:27 AM Subject: 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 _______________________________________________ SableVM-devel mailing list [email protected] http://sablevm.org/lists/control/listinfo/sablevm-devel