[prev in list] [next in list] [prev in thread] [next in thread] 

List:       e-lang
Subject:    [e-lang] Another E bug: "not alloced: 3"
From:       Mark Miller <markm () cs ! jhu ! edu>
Date:       2004-11-19 20:43:47
Message-ID: 419E5B03.1000202 () cs ! jhu ! edu
[Download RAW message or body]

Nilo Rivera wrote:
> Hi Mark,
> 
> Remember I told you about the problem that, if you start the tree too 
> fast, it does not form well, but a slower startup is fine.  Well, I 
> tried the code in barley and it gives me more information than when 
> running in window with the same problem (windows does not tell me 
> anything is wrong).  What does this means?


I suspect you're experiencing the silence on Windows because E is correctly 
writing the diagnostics into a trace file in your TraceLog_dir directory, 
whereas I suspect you're seeing the diagnostic on barley because you don't 
have a ~/.e/etrace directory. Could you please check both of these guesses and 
respond to me privately? Thanks.

As to the error itself (shown below), the diagnostic "not alloced: <integer>" 
is definitely an internal bug in E. (Specifically, in the component of E that 
handles E's network protocol, CapTP.) Until I understand this better, I can't 
yet suggest a work-around. But at least I think I now have a reproducible case 
of this, and will try to debug it. Sorry for the inconvenience. As I have 
news, I'll let y'all now.


> === 2004-11-19T02:06:31.390Z 
> (CapTPConnection.whyNoDeliverOp:CapTPConnection.java:867) WRN
> captp: whyNoDeliverOp(-2, <Far ref>,
>  0, provideFor, ???)
> --vvvv--
> not alloced: 3
> 
> 
> java.lang.IllegalArgumentException: not alloced: 3
>        at net.captp.tables.CommTable.mustBeAlloced(CommTable.java:147)
>        at net.captp.tables.CommTable.get(CommTable.java:285)
>        at 
> net.captp.jcomm.CapTPConnection.getIncoming(CapTPConnection.java:580)
>        at net.captp.jcomm.IncomingDesc.dereference(IncomingDesc.java:66)
>        at net.captp.jcomm.CapTPReviver.substitute(CapTPReviver.java:36)
>        at 
> org.erights.e.elib.serial.UnserializationStream.resolveObject(UnserializationStream.java:65) 
> 
>        at 
> java.io.ObjectInputStream.checkResolve(ObjectInputStream.java:1311)
>        at 
> java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1264)
>        at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1593)
>        at 
> java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1261)
>        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:322)
>        at 
> net.captp.jcomm.CapTPConnection.receiveMsg(CapTPConnection.java:726)
>        at 
> net.captp.jcomm.CapTPConnection.processMessage(CapTPConnection.java:693)
>        at 
> net.vattp.data.VatTPConnection.newIncomingMsg(VatTPConnection.java:716)
>        at net.vattp.data.DataPath.newIncomingMsg(DataPath.java:685)
>        at net.vattp.data.DataCommThunk.run(DataCommThunk.java:216)
>        at org.erights.e.elib.vat.PendingCall.innerRun(PendingCall.java:75)
>        at org.erights.e.elib.vat.PendingEvent.run(PendingEvent.java:76)
>        at 
> org.erights.e.elib.vat.HeadlessRunner.run(HeadlessRunner.java:176)
>        at java.lang.Thread.run(Thread.java:536)
> 
> --^^^^--
> 
> 


-- 
Text by me above is hereby placed in the public domain

     Cheers,
     --MarkM


_______________________________________________
e-lang mailing list
e-lang@mail.eros-os.org
http://www.eros-os.org/mailman/listinfo/e-lang
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic