public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Andrew John Hughes <gnu_andrew@member.fsf.org>
Cc: classpath@gnu.org, tromey@redhat.com,
	mauve-discuss@sources.redhat.com,
	 Robert Lougher <rob.lougher@gmail.com>
Subject: Re: Mauve patches for SpinnerListModel
Date: Sun, 05 Sep 2004 19:27:00 -0000	[thread overview]
Message-ID: <1094412368.2117.98.camel@localhost.localdomain> (raw)
In-Reply-To: <20040819003736.GA24589@middle-earth.co.uk>

[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]

Hi,

On Thu, 2004-08-19 at 02:37, Andrew John Hughes wrote:
> Attached is a series of Mauve tests for SpinnerListModel
> to go in the directory gnu/testlet/javax/swing/SpinnerListModel.
> What do I do about adding these?

You post them to mauve-patches@sources.redhat.com :)
And/Or you ask Tom for permission to check them in yourself.

> Also, does anyone have any idea as to why Mauve only seems to test java.io and
> java.net when I run make check?  Using ant, I can get it to compile all the tests
> but it segfaults in java.lang.reflect.Array.newInstance.

For these kind of questions there is the
mauve-discuss@sources.redhat.com mailinglist.
Personally I don't use ant but the batch_run and runner script (see the
README) which should automatically run all the tests. The README also
has some more examples on how to run mauve "the traditional way" (make
and autotools).

The crash in Array.newInstance() is a bug in jamvm (which I assume you
are using). CCed Robert. I thought I had reported it earlier, but maybe
I forgot. This is in the last multi-dimensional test:

    val = 0;
    try
      {
        x = Array.newInstance(String.class, new int[]
          {Integer.MAX_VALUE, Integer.MAX_VALUE});
        val = 1;
      }
    catch (OutOfMemoryError e)
      {
        val = 2;
      }
    catch (Throwable t)
      {
        harness.debug(t);
        val = 3;
      }
    harness.check(val, 2);

gdb backtrace below.

This is why I run the batch_run script since it will just ignore such
crashes and go on with the next test.

Cheers,

Mark

isInstOfArray0 (array_class=0x401bd440, test_elem=0x0, test_dim=2) at cast.c:52
52              return IS_INTERFACE(CLASS_CB(array_elem)) ?
(gdb) bt
#0  isInstOfArray0 (array_class=0x401bd440, test_elem=0x0, test_dim=2)
    at cast.c:52
#1  0x0804ac5b in arrayStoreCheck (array_class=0x0, test=0x0) at cast.c:85
#2  0x0805227e in executeJava () at interp.c:820
#3  0x0804e532 in executeMethodVaList (ob=0x0, class=0x0, mb=0x8119260,
    jargs=0xbfffdd40 "\034\uffff\032@\001") at execute.c:66
#4  0x0804e3c6 in executeMethodArgs (ob=0x0, class=0x0, mb=0x0) at execute.c:38
#5  0x080565d2 in main (argc=2, argv=0xbfffdde4) at jam.c:278

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

       reply	other threads:[~2004-09-05 19:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040819003736.GA24589@middle-earth.co.uk>
2004-09-05 19:27 ` Mark Wielaard [this message]
2004-09-06  2:36   ` Robert Lougher
2004-09-06 16:24   ` Thomas Zander

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1094412368.2117.98.camel@localhost.localdomain \
    --to=mark@klomp.org \
    --cc=classpath@gnu.org \
    --cc=gnu_andrew@member.fsf.org \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=rob.lougher@gmail.com \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).