harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Volosyuk" <ivan.volos...@gmail.com>
Subject Re: [drlvm] HARMONY-1559 patch causes SIGABRT in VM code
Date Mon, 02 Oct 2006 13:43:44 GMT
Ok, I will look at the issue today.
--
Ivan

On 10/2/06, Alexey Varlamov <alexey.v.varlamov@gmail.com> wrote:
> 2006/10/2, Alexey Varlamov <alexey.v.varlamov@gmail.com>:
> > 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
> > 0x(nil) referenced from object = 0x0x41253d24
> > 0x(nil) referenced from object = 0x0x41253d24
> >  [THIS]: java/lang/Class
> > [METHOD <native>]: java/lang/VMThreadManager.wait(Ljava/lang/Object;JI)I
> > 0x0x414e9530 referenced from root = 0x0x52721f3c info = -2147480576
> > 0x0x414e9530 info = -2147480576
> > 0x0x414e9530 is java/lang/FinalizerThread$FinalizerWorkLock
> > move 0x0x414e9530 to 0x0x41253d44 info = -2147480575
> >  [THIS]: java/lang/FinalizerThread$FinalizerWorkLock
> > [METHOD 4 2]: java/lang/Object.wait()V
> >  Stack[0]
> > NPE or SOE detected at 0x4114fe18
> > ---------------------------
>
> I fixed endless looping in HARMONY-1653. And now we need to understand
> why the SIGSEGV occurs. Is it corrupted stack or smth else?
> Ivan, could you please look into this?
>
> --
> Alexey

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org


Mime
View raw message