Re: [Sablevm-developer] Problems with 1.0.3 - java/lang/UnsatisfiedLinkError

[Etienne M. G. <eti...@uq...>]

Hi Grzegorz,

It would be interesting that you also generate method, instruction and
exception traces as I have suggested to Mark, with the 1.0.3 version
(with or without the xxx_Runtime.c patch).  I'm really intrigued by
the fact that 1.0.3 does not work for you, but 1.0.1 does.

Maybe I should investigate using "cvs diff"...  I'll give this a
*brief* look.

Etienne

On Tue, Aug 20, 2002 at 11:53:14PM +0200, Grzegorz Prokopski wrote:
> W li?cie z wto, 20-08-2002, godz. 23:30, Mark Wielaard pisze: 
> > Hi,
> > 
> > On Tue, 2002-08-20 at 21:10, Grzegorz Prokopski wrote:
> > > W li?cie z wto, 20-08-2002, godz. 20:55, Mark Wielaard pisze: 
> > > > I am going to try to update to the CVS version and try again.
> > > If it fails - try 1.0.1 and report the result please.
> > Then I downloaded the 1.0.1 versions:
> > sablevm-1.0.1.tar.gz, sablevm-class-library-1.0.1.tar.gz and
> > sablevm-native-library-1.0.1.tar.gz.
> > Unpacked sablevm-1.0.1.tar.gz, unpacked the other two archives inside
> > the sablevm-1.0.1 directory and replaced the system.h, system.c and
> > jni_system_specific.h files with the patched CVS versions. This produced
> > a binary that got a little bit further as can be seen in the attached
> > output file but gives a java/lang/ExceptionInInitializerError at the
> > end.
> yes, but it got much further it seems.
> 
> > I hope someone else will get better results. I will probably not have
> > more time to play with this stuff before the weekend. If you have
> > specific things you want me to try out please let me know, but I won't
> > have time to debug this on my own right now.
> I'd happily try it myself, but unfortunatelly debian machines admins
> still haven't installed needed packages on the only PowerPC that is
> freely available to debian developers.
> [I don't have access to any other PowerPC machine]
> 
> Idea:
> The problem may be because the assemmbler part may not be working like
> it should. If that's the case - please disable assember code for
> a moment and try that "plain C" version of "test&swap" function (which
> should never ever be used for real ;)
> 
> Please pass --enable-debugging-features option to configure, so that
> we knew you're using most "safe" settings.
> 
> That's very simple test.
> I am curious if that makes any difference and if results are always
> the same for every run.
> 
> Regards
> 
> 						GBP
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Sablevm-developer mailing list
> Sab...@li...
> https://lists.sourceforge.net/lists/listinfo/sablevm-developer

-- 
Etienne M. Gagnon                    http://www.info.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/