[Mono-list] Test failure

Mark Crichton crichton@gimp.org
Mon, 30 Sep 2002 15:10:18 -0400


--HeFlAV5LIbMFYYuh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

* Ferguson, Neale (Neale.Ferguson@SoftwareAG-USA.com) [020930 14:50]:
> the mono_create_method_pointer code that tramp.c would emit?

Don't know, but let me compare with my results from Sparc.  The code is
probably the same.  Also, it might also highlight potential alignment
issues in mono, which I know are lethal on Sparc (don't know about
S/390).

> Testing exception6.exe... failed 2048 (8) signal (0).

I get the same exact error on Sparc.  If you look at the C# code for
exception6.cs, look for a "return 8;", and that's where the code fails.

Why it fails I have no idea.

> Testing pinvoke2.exe... failed 34304 (134) signal (0).
> Testing pinvoke3.exe... failed 34304 (134) signal (0).
> Testing pinvoke4.exe... failed 34304 (134) signal (0).

You're catching a SIGTRAP.  For pinvoke2, I'm getting an error there
since I cannot handle MONO_TYPE_VALUETYPE where its size != 4.  This is
where PPC does some memcpy trickery.  I don't know if this would work
on Sparc or S/390.  It might.

pinvoke3 and 4 fail for me with error 255.  I've been told that is
somewhat normal, but I don't know why.  Lupus, can you explain that one
to me?

> Testing pinvoke6.exe... failed 65280 (255) signal (0).
> Testing pinvoke7.exe... failed 65280 (255) signal (0).

See above.

> Testing pinvoke8.exe... failed 34304 (134) signal (0).

For me, I put an assert, since I cannot handle a value type as a return
value from a delegate.  No clue on how I'll fix that one.

> Testing cattr-object.exe... failed 512 (2) signal (0).

Passes for me.  Look at the source code for cattr-object.cs.  Why that
one isn't working, I have no idea.

> Testing jit-int.exe... failed 65280 (255) signal (0).

Fails for me as well.  No idea either.

> Testing appdomain2.exe... failed 1024 (4) signal (0).
Failure here as well, but the error is 255.  Maybe you have a
trampoline problem there.

> Testing vararg.exe... failed 34304 (134) signal (0).

Check your vararg.exe.stdout.  See if you get a line:
** ERROR **: file loader.c: line 283 (method_from_memberref): should
not be reached

I get that as well, and this is another of the boggling bugs.

> Testing marshal2.exe... failed 256 (1) signal (0).
> Testing marshal4.exe... failed 34304 (134) signal (0).
> Testing thread5.exe... failed 256 (1) signal (0).
> Testing thread6.exe... failed 35328 (138) signal (0).

I get failures here as well, mostly due to my trampoline code not being
able to handle strange size VALUETYPEs.  You might want to check to see
if that code works.

Mark

--HeFlAV5LIbMFYYuh
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (SunOS)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj2YoZkACgkQOfj2Ja/u/oArkQCg2Hzmax7sNUwiIPFvISXogcHC
MB4An13IEfpSAktGOsxJrKbHp7R/iYOg
=z7/1
-----END PGP SIGNATURE-----

--HeFlAV5LIbMFYYuh--