OSDev.org

Obviously, my OS does not crash frequently enough.

xyzzy wrote:Turns out it's actually a bug with QEMU's Cocoa frontend, it works fine anywhere else

Argh! I can confirm this.
I chased a bug in my VBE code for a few days and didn't find anything. This explains why.

Also, have a look at this screenshot:
http://lockerz.com/s/120621654
On the left side you can see VMware, VirtualBox is in the middle and qemu on the right.
All created by the same code, counting a 16 bit integer from 1 up and using it as a color value. Something is not right there

How do people manage to get pictures from a crashed OS? Is it because they run on emulators rather than real hardware?

I got it!

An OS crash with Bochs:



Updated bochs panic screen with the newest version:

Divide error Sing Gdt 0000
EAX=0007EEA0 EBX=00000FC4 ECXÂ010D18C7 EDX=00000000 ESI=00000000 EDI=00000000
EPC=0000C0EF ESP=00000800 EBP=00007B00 NC PE NA ZR PL EI UP NV PR PM
CS=0030 SS=0188 DS=EEA0 ES=0030 FS=F040 GS=0000

Bochs log:

00434348346e[CPU0 ] LLDT: doesn't point to an LDT descriptor!

I'm absolutely certain that this is an emulation error, and not something real!

rdos wrote:How do people manage to get pictures from a crashed OS? Is it because they run on emulators rather than real hardware?

Yes, it's the easiest way. I for one lack a good camera to show off all the bugs in my video drivers (including some that would need an audio recording)...

rdos wrote:I'm absolutely certain that this is an emulation error, and not something real!

While there are bugs in bochs, I very much doubt whether you're right :).


JAL

Hi,

Combuster wrote:(including some that would need an audio recording)...

Wondering whether that's because of the monitor bursting, or the neighbors screaming due to the fire..

Coming back to the topic, I got some really stupid bugs with me, though I forgot to take screenshots. One of these is that I switched to mode 0x12 instead of 0x13, and kept wondering why everything was so borked up..

Regards,
Shikhin

Shikhin wrote:

Combuster wrote:(including some that would need an audio recording)...

Wondering whether that's because of the monitor bursting, or the neighbors screaming due to the fire..

Oranos wrote:Wondering whether that's because of the monitor bursting

Was once told of a chip in CRT screens that if malfunctioning, blinds viewers? Or just explodes either one sucks

I've made many modifications in threading lately, and it works fine with apic timer. So I was wondering what's with the good old PIT driver? It should make no difference, but I gave it a try, so I recompiled my kernel in legacy mode (hence the "L" in the right upper corner of screen). As it turned out, after a couple of thread switches, it suddenly messes up the stack very badly, that leads to executing an error message string in a different method... I'm not sure whether debugging worth it, maybe it's time to drop PIT support?

p.s. for those in doubt: you can relax, this screen is not a fake.

GhostXoPCorp wrote:Was once told of a chip in CRT screens that if malfunctioning, blinds viewers? Or just explodes either one sucks

Either one is also an interesting and unique way to deal with those annoying neighbours...


@turdus: Are you using a custom font to display those little logos in the bottom corners of the screen?

Blacklight wrote:@turdus: Are you using a custom font to display those little logos in the bottom corners of the screen?

Yep. I've written a small javascript utility to generate bitmap in source format (asm, c and pascal). I've draw the logo with it and copy'n'paste the code into my source. You can set it up via BIOS (see RBIL) or directly programming vga registers.

Forgot to change my console functions to account for a bigger framebuffer.

ben1066 wrote:Forgot to change my console functions to account for a bigger framebuffer.

Doesn't really look like the OS going crazy. Just some mis-aligned texts.

Chandra wrote:

ben1066 wrote:Forgot to change my console functions to account for a bigger framebuffer.

Doesn't really look like the OS going crazy. Just some mis-aligned texts.

It's the closest to crazy my OS gets, which, for the most part, is a good thing