OSDev.org

Asmadian thinks it's funny when there's a page fault while initializing multitasking (probably in move_stack()):

Man, weird stuff. First the weird VFS bug where gcc decided not to tell me about a syntax error, now this.

Calling some of the functions to print stuff to the screen with a corrupted stack lead to this:



It's actually kind of pretty in a way but finding the problem took a while :p.

It look nice!. Save somewhere a copy of your OS image at this stage of development. I save my failed images. This way latter I will can see the progress.

Graham wrote:Calling some of the functions to print stuff to the screen with a corrupted stack lead to this:

....

It's actually kind of pretty in a way but finding the problem took a while :p.

Make them fall down to the bottom of the screen .

EDIT: did anyone see the heart from the first time they looked?

Or rise up!

Even better, first crash, then rise a copy up with alpha blending enabled

awesome thread.

this is what happened when i had a dumb mistake that loaded up the code for a new process in my 16-bit real mode multitasking OS... into the base video RAM 0xB800.



fun!

miker00lz wrote:this is what happened when i had a dumb mistake that loaded up the code for a new process in my 16-bit real mode multitasking OS... into the base video RAM 0xB800.

Looks like you need a paper towel. =x

eddyb wrote:EDIT: did anyone see the heart from the first time they looked?

I didn't notice that at first either :p

berkus wrote:Running self-modifying code in screen RAM should be fun to watch.

Yes but it has to produce always something with a meaning XD... This is a cool idea for a contest XD

Karlosoft wrote:Yes but it has to produce always something with a meaning XD... This is a cool idea for a contest XD

How about running code in 4-plane 16-colour mode, and have the code run without crashing regardless of which plane is enabled. Or something :)


JAL

Recently restarted my attempt to write an OS, and look what i got:



And no: i realy have no idea what happened, but my IO::VGA::set_mode() got called!

Ops I rendered the font in the wrong way XD

Not the first 1 to do tht, I might add. If you can keep the code, add a cool backwards text command, which does as you see there. turn a bug into a feature. could be fun!

Sure I can XD! Thank you for the suggestion I added this crazy feature to Smile (my OS ) and I'm going to add the code to rotate the screen (portrait/landscape view).