I have fixed a problem in gc_alloc(), see HARMONY-1661. After that
test passes on my computer.
--
Ivan
On 10/2/06, Ivan Volosyuk <[EMAIL PROTECTED]> wrote:
Ok, I will look at the issue today.
--
Ivan
On 10/2/06, Alexey Varlamov <[EMAIL PROTECTED]> wrote:
> 2006/10/2, Alexey Varlamov <[EMAIL PRO
Ok, I will look at the issue today.
--
Ivan
On 10/2/06, Alexey Varlamov <[EMAIL PROTECTED]> wrote:
2006/10/2, Alexey Varlamov <[EMAIL PROTECTED]>:
> Trace logging gives some more details:
>
> GC enumeration in interpreter stack:
>
> 0x0x413ee828 referenced from root = 0x0x52
This issue is accompanied now with similar crash on Windows (interpreter):
[echo] RUNNING : java.lang.RuntimeTest
[junit] This application has requested the Runtime to terminate it in an
unu
sual way.
[junit] Please contact the application's support team for more
information.
[junit]
2006/10/2, Alexey Varlamov <[EMAIL PROTECTED]>:
Trace logging gives some more details:
GC enumeration in interpreter stack:
0x0x413ee828 referenced from root = 0x0x52721d4c info = 0
0x0x413ee828 info = 0
0x0x413ee828 is java/lang/Class
move 0x0x413ee828 to 0x0x41253d24 info
Trace logging gives some more details:
GC enumeration in interpreter stack:
0x0x413ee828 referenced from root = 0x0x52721d4c info = 0
0x0x413ee828 info = 0
0x0x413ee828 is java/lang/Class
move 0x0x413ee828 to 0x0x41253d24 info = 1
0x(nil) referenced from object = 0x0x41253d24
Today this crash is reproduced quite stably during "build.sh
kernel.test". But it always passes if run standalone :(
Regarding 1559 patch, I looked through it and found nothing
suspicious. The only change to interpreter itself was actually
preliminary fix for Harmony-1561. This is not good (1559
2006/9/28, Elena Semukhina <[EMAIL PROTECTED]>:
The issue has gone away for me too, false alarm possibly...
Unfortunately the alarm was not false. Today I got the same failure:
...
[junit] SIGABRT in VM code.
[junit] java:
/nfs/ins/proj/drl/coreapi/avarlamo/harmony/linux.ia32/svn-repo/
The issue has gone away for me too, false alarm possibly...
Elena
On 9/28/06, Pavel Rebriy <[EMAIL PROTECTED]> wrote:
I've just repeated kernel.test run today several times on fresh build, and
tests pass.
It's a very stange crash. Execute JIT stack iterator in interpreter mode..
It's outlandis
I've just repeated kernel.test run today several times on fresh build, and
tests pass.
It's a very stange crash. Execute JIT stack iterator in interpreter mode..
It's outlandishly.
On 28/09/06, Alexey Varlamov <[EMAIL PROTECTED]> wrote:
I do not observe this crash - I ran kernel tests yesterday
I do not observe this crash - I ran kernel tests yesterday and today
several times, no crashes on interpreter on Linux IA32...
2006/9/28, Gregory Shimansky <[EMAIL PROTECTED]>:
On Wednesday 27 September 2006 16:35 Geir Magnusson Jr. wrote:
> :)
>
> Is there an easy fix, or do we rollback?
Inte
On Wednesday 27 September 2006 16:35 Geir Magnusson Jr. wrote:
> :)
>
> Is there an easy fix, or do we rollback?
Interpreter is meant for the development for the most part. I think it is not
critical if it doesn't work for a short time. It is not used by most of the
community anyway because the
I just wondered what changed after yesterday, rolled back HARMONY-1559 patch
and so discovered cause-effect relation.
I can say nothing about the fix, we should ask the patch submitter :(
On 9/27/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
:)
Is there an easy fix, or do we rollback?
g
:)
Is there an easy fix, or do we rollback?
geir
On Sep 27, 2006, at 8:32 AM, Elena Semukhina wrote:
Hi all,
after HARMONY-1559 patch has been committed, kernel unit test
RuntimeTest
started to fail on linux in the interpreter mode.
It loops with the message
[junit] SIGABRT in VM cod
Hi all,
after HARMONY-1559 patch has been committed, kernel unit test RuntimeTest
started to fail on linux in the interpreter mode.
It loops with the message
[junit] SIGABRT in VM code.
[junit] java:
/nfs/ins/proj/drl/coreapi/esemukhi/git/drlvm/trunk/vm/port/src/lil/ia32/pim/stack_iterator
14 matches
Mail list logo