|
Here
comes a snapshot of Clicker's early stage of boot-up. At this point, the system has entering the kInit() function and has performed the critical basic initialisation (turning into pmode, initializing interrupt management, setting up display structures) It's gently waiting you to press space to continue to boot. |
| This
is a snapshot of Clicker's debug console. When the system is running, it dumps loooooot of messages on the so-called "green console" so that you can follow "step by step" progression of the system even if you don't have a powerful virtual machine. Of course, this slows down the execution. You can usually select the messages you want to appear on this console, but only when the "debug" module has been loaded - and on my 1Ghz machine, it takes bochs about 5 minutes to reach that point (even more)!! Fortunately, you can compile the kernel without __DEBUG__ to make it faster. Note that on a 300MHz "real" system, reaching the debug screen don't even take a second !-) |
|
|
Sometimes,
when you are really too tired to code, you can see clicker stopping itself
and showing three columns of hex number: a stack dump! Don't trust it even if it says "Termination Successful": it just means you're back to ms-dos and that you should be able to run analyzis tools. One of them - log.com - allow you to look at the system log. Hereby is a snapshot of that log after a very werdy crash in the BOCHS (never seen something that weird on real hardware). Log usually stores warning messages. Sometimes, a thread crash and you'll have a nice summary of its state (including fault report, backtrace, registers content, etc.) Here, there have been so many of such problems (and curiously, without a valid thread id !?) that you don't see anything else on the log. |
