aegisvm-devel

[Aegisvm-devel] patches to apply to be able to run mauve

[Gildas B. <gb...@al...>]

Hi,

As I already told you, I've been trying to run mauve on aegisvm but with the 
current cvs version mauve doesn't even bootstrap.
I finally got it running though.

I had a really quick run at some of these tests and as you might already 
guess, there are quite a few which fail with aegisvm but at least now we've 
got an extensive testsuite to find and correct the problems :)

So to be able to run mauve you have to apply the following patches:
- jni.diff (patch that I already sent)
- bug.diff (fixes two important bugs in aegisvm. the commentaries in the 
patch should be self explanatory)
- other.diff (implements a few other things needed by mauve)
- finalize-hack.diff (nasty hack that comments out "throw new 
FeatureNotYetImplementedError()" in runFinalization() in java.lang.System. 
It's commented out because I don't know how to implement it properly.)
- jpr.diff (patch to j_utf8_scan_qualified_name() and 
j_utf8_scan_java_simple_class_name(). I'm not sure these are the right 
fixes for the problem but I know there definitely is a problem with name 
recognition as mauve and several other programs expect JVMs to accept in 
there command line names like foo.bar as a java program to execute)

Enjoy :)

--
Gildas

Re: [Aegisvm-devel] patches to apply to be able to run mauve

[Philip F. <pw...@us...>]

Hi,

I have just committed the following:

> - other.diff (implements a few other things needed by mauve)
> - finalize-hack.diff (nasty hack that comments out "throw new 
> FeatureNotYetImplementedError()" in runFinalization() in java.lang.System. 
> It's commented out because I don't know how to implement it properly.)

What is remaining are two particular patches:
(1) I am not sure what the patch on interpret.c (invokeinterface code)
    is for.  Would you mind to explain a bit more?  As I understand
    from the JVM spec the narg operand only counts the arguments
    but not the objectref.  Am I missing something?
(2) Concerning the following patch:

> - jpr.diff (patch to j_utf8_scan_qualified_name() and 
> j_utf8_scan_java_simple_class_name(). I'm not sure these are the right 
> fixes for the problem but I know there definitely is a problem with name 
> recognition as mauve and several other programs expect JVMs to accept in 
> there command line names like foo.bar as a java program to execute)

    Do you mean that, say the main() method of a Java program resides
    in class foo.bar, typing "aegisvm foo.bar" does not properly
    start the program?

Thanks.

Philip

--
Philip W. L. Fong            pw...@us...
The Aegis VM Project         http://aegisvm.sourceforge.net

The Aegis VM Project is an on-going effort to implement a lightweight,
secure JVM.  It will eventually feature a modular architecture, Proof
Linking, that supports pluggable verification modules.

Re: [Aegisvm-devel] patches to apply to be able to run mauve

[Gildas B. <gb...@al...>]

On Saturday 27 July 2002 01:14, Philip Fong wrote:
> 
> I have just committed the following:
...
> 
> What is remaining are two particular patches:
> (1) I am not sure what the patch on interpret.c (invokeinterface code)
>     is for.  Would you mind to explain a bit more?  As I understand
>     from the JVM spec the narg operand only counts the arguments
>     but not the objectref.  Am I missing something?

I think the JVM spec is not clear there. This is also what I understood at 
first, but I have a testcase that proves the objectref is in fact included 
in the count. Have a look at the attached java files and try them with and 
without the patch, you'll see :)
(I myself used AE_DEBUG_INSTR to find out what was really going on.)

> (2) Concerning the following patch:
> 
> > - jpr.diff (patch to j_utf8_scan_qualified_name() and 
> > j_utf8_scan_java_simple_class_name(). I'm not sure these are the right 
> > fixes for the problem but I know there definitely is a problem with name 
> > recognition as mauve and several other programs expect JVMs to accept in 
> > there command line names like foo.bar as a java program to execute)
> 
>     Do you mean that, say the main() method of a Java program resides
>     in class foo.bar, typing "aegisvm foo.bar" does not properly
>     start the program?
> 

yes, if I use aegisvm foo.bar I will have the following error:
resolve.c:303: failed assertion: thread != 0 && classname != 0 && 
j_utf8_is_class_name(classname)
because j_utf8_scan_qualified_name() doesn't deal with J_ASCII_period.

The fix to j_utf8_scan_java_simple_class_name() is also needed if you want 
to pass test names to mauve as foo/bar/foobar instead of foo.bar.foobar.

Regards,

--
Gildas