OSDev.org

I did some work on my editor, implementing copy-and-paste and other fun stuff. I also tried to implement a soft 80-character margin because I like to keep my lines shorter than that. Something went horribly wrong.

https://cs.au.dk/~sortie/sortix/crazy-o ... ng-bug.png [1920x1080 resolution]

Looks like I negated the is-there-a-valid-character-to-render and invoked lots of undefined behavior combined with buffer overflowing reads.

finarfin wrote:Nothing special,

only a bug in echo, but nice effect

You put arguments in a wrong way.

This was a very dumb mistake in increasing a pointer. I defined char* as _pch and declared a _pch var to use as a printable string. each time I needed to increase it but i forgot to put that * before increasing the pointer and it was always printing random characters and it was created an infinit loop I guess!!

I attempted to make my OSMesa port compile some nice GLSL shaders, which resulted in a major explosion of debug output.



Time to fix printf.

I have some exciting issues (that I still don't fully understand) that cause fun rendering glitches, but only in QEMU. VMware is fine.

pcmattman wrote:I have some exciting issues (that I still don't fully understand) that cause fun rendering glitches, but only in QEMU. VMware is fine.

{img removed}

My eyes!

Looks like a very fine-grained random dot stereogram

It seems I can't do anything bad in userspace... Even though I didn't acheive neither a system call nor memory management, I got my OS protection work.

Just a couple of things which happened recently...

Finally got to a point where I can print fabulous error screens like you guys:

When trying to get things to work in VirtualBox, the FAT driver tried to update the last access date for a file on an apparently write protected disk (presumably because the image file was already mounted in ImDisk). Selecting the drive letter that the file is mounted to instead of the file itself doesn't help either, but the error message becomes slightly different.

When my BOOT16.DLL goes missing...............
[LOL]

My description

Changed something in the bootloader which caused half of my data to go missing

For some reason, this didn't cause total havoc, but it did cause my calls to clearScreen to stop working. So there's some stuff from the bootloader still hanging in the background. That error was created on purpose, to test my interrupt handling.



This is how it should look:


I don't really understand what was going on, but it's fixed now

Writing to a framebuffer and incrementing the pointer wrong… that's fun, I guess?