Well, I've been doing quite a bit of follow-the-code, trying to figure out
why the trunk kernel, when compiled and then trunk-aoted, crashes. (My
biggest problem being, having not written the IDT code, and with it not
being fully documented ATM, I really didn't know what was going on.)
The ISR_DEFAULT_HANDLER is getting called, because an interrupt is being
called that hasn't been assigned an appropriate handler.
This may or may not be news: the interrupt is number 06, which Ralf Brown's
Interrupt List - http://www.ctyme.com/intr/int-06.htm - indicates is an
invalid opcode.
Unless someone messed something up with X86.Asm.XXXX() calls in the kernel,
this is definitely an AOT issue. As I get time, I'll tinker more in the
future, but I'm at a loss at this point because I wouldn't know how to take
the code pointer register (which one is it, anyway...lolz) and figure out
how to match that up to an x86 asm text file that the AOT is capable of
outputting. Any pointers, Chriss? xfury?
*Meanwhile*, I will look into writing more descriptive default handlers for
the various CPU exceptions...
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
