OSDev.org

Let's dig up this thread again . Just found it while searching for something.

Here's the latest progress in my 'old' kernel (before redesign, UNIX-like). It can run GCC and display a PNG image using libpng/zlib and the VBE driver:



And here's the not-so-interesting new microkernel running 2 servers (the process manager gets a copy of the process table from the kernel at startup which it prints out here) communicating via my IPC code.


EDIT: Oops, put the wrong image URL in for the last screenshot

1337 congratulations, having gcc and png support is cool.

Wow, Exclaim has come a long way!

[quote="Pype.Clicker"]
^^ the paging debugger with content inspection

SWEET! Nice PC (can I call you PC? )

This is exactly the type of application I'm looking at writing very soon. Extremely useful (I'm not much of a fan of debugging paging issues via manual/textual dumps of page tables

--Jeff

Exclaim looks great, Alex. Nice work.

Hmm.....heres an updated version:


-JL

did you setup the screen mode in pmode or in real mode?

Here's a screen of Beryllium from the beginning of this month - nothing has changed since then except for a few attempts to fix paging. I'm going to rewrite after formatting my hard drive.


And one of my absolutely pointless OS written in Assembly with a broken PutChr function that's been driving me nuts for the past two days:

trolly wrote:did you setup the screen mode in pmode or in real mode?

I set the screen mode in pmode.

Adapted from Chris Giese's modes.c code, I got rid of all the vga mode stuff, I'm not bothering with that until later.

Would you like a copy? It's stand-alone, except all you really need is inb, outb, inw and outw.

-JL

Jeremiah Griffin: Have you posted about that putch problem in another thread, maybe someone can see what's wrong with it?

And, thanks for the nice comments about Exclaim

OK, I give in. Here's a screenshot from Pedigree's kernel debugger, which is currently the only remotely pretty or entertaining part of it!



^^ Main debugger screen, showing the dump and disassemble commands, as well as command completion and hint text in the bottom row.



^^ Log viewer. The [0000000] on the left is actually a timestamp, but because all those log messages were generated before the PIT is initialised, they're all zero. The colour depicts the severity of the message - green: notice, yellow: warning, purple: error, red: fatal.



^^ Execution tracer. Notice the backtrace at the bottom and automatic c++ symbol demangling as well as function parameter rendering.



^^ The debugger also works via serial, too.

Nice...I didn't know you guys had got much past the planning stages yet, but you already have much more of a UI than me and I'm jealous of the debugger too!

Cheers,
Adam

Me too. I've been thinking of implementing a debugger but only basic text output, not something fancy like that.

Thanks guys, me and bluecode have put rather a large amount of work to get it where it is, but there's still miles to go!

Cheers,

James

AlexExtreme wrote:And here's the not-so-interesting new microkernel running 2 servers (the process manager gets a copy of the process table from the kernel at startup which it prints out here) communicating via my IPC code.

I don't know about you, but I think having multitasking with IPC implemented is a lot more interesting than displaying a PNG using VBE.