Hi Thomas;
Thomas Bocek wrote:
> while devoloping the vga driver I executed some of the code in text mode
> to see what's wrong and there I had some jbHeap errors and once a <00000000>.
> Perhaps the error is the same, but I'm not sure. I just said (wanted
> to say) that this were the two errors I saw while developing the driver.
The <00000000> things are actually interrupts (?!) -- interrupt zero, actually
-- that occur but have no registered/assigned handler routine. And, of course,
I don't have my books in front of me now, so I can't tell you what interrupt
that is. I'll check up on this. Weird.
The only error the heap currently can detect is an "out of memory" error. Is
this the other problem you're seeing?
> BTW the line:
> String[][] test={{"0x0D10","test","Matrox Impression Plus","test"}};
> does an jbHeap::allocate error too.
Hmm... Either the heap really thinks it's out of memory, or it could be a bug
in the Java array stuff (which is kind of built-in).
Might I be so bold as to ask you to please let me and/or Todd know about such
easily-reproducible errors? They're wonderful in that they will help us to
debug jjos and decaf, and it sure is better to track down bugs like that than it
is to let them quietly lie dormant until the rear up and bite us on the
collective ass.
Thanks! I'll look into both of these ASAP (probably Thursday at the earliest,
Friday at the latest).
By the way, George (Hi, George!) was kind enough to send me a cut at the
conservative GC heap implementation, which I'll also be looking into ASAP.
Hopefully, jjos+decaf should stay up long enough to be "interesting" after it's
integrated.
-jm
--
==== John Morrison ==== MaK Technologies, Inc.
==== Chief Technology Officer ==== 185 Alewife Brook Pkwy, Cambridge, MA 02138
==== [EMAIL PROTECTED] ==== http://www.mak.com/welcome.html
==== vox:617-876-8085 x115 ==== fax:617-876-9208
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
