OSDev.org

I accidentally put spawn() in a loop.
At least I know that my scheduler works nicely.
As does the rest of my multitasking stuff.

greyOne wrote: At least I know that my scheduler works nicely.

I'm guessing that it's printing off process ids?

p0s1x wrote:Nothing boot failed, because it's true.

Very nice!

sounds wrote:

p0s1x wrote:Nothing boot failed, because it's true.

Very nice!

Thanks

At least I know my nice register dump in the kernel panic works... I sometimes call it the Schizophrenic Screen of Death.

phillid wrote:I sometimes call it the Schizophrenic Screen of Death.

They have multiple personality disorder.

m12 wrote:

phillid wrote:I sometimes call it the Schizophrenic Screen of Death.

They have multiple personality disorder.

No, thanks, I'm fine!
Me too!

m12 wrote:They have multiple personality disorder.

The panic screen of my OS loader is quite fun too, it has a logo and contains a sentence passed a sargument to the panic() function, or when none is passed, the default one, which is the sentence "Hey! I pissed on myself !" but in french, and written as would say it a Spanish man trying to speak french for first time

I can't screenshot this, my kernel panicked.
I mean the Windows kernel that is. Blue screen and everything.
My kernel just went belly up it seems.

So much for Virtual Box being safe.

greyOne wrote:I can't screenshot this, my kernel panicked.
I mean the Windows kernel that is. Blue screen and everything.
My kernel just went belly up it seems.

So much for Virtual Box being safe.

The danger of hardware virtualization. Sometimes this happens if you clobber improperly mapped MMIO or ACPI non-reclaimable space.

Working on animations in my compositor, and I accidentally told the background window to run the "map out" effect:



... I neglected to check which window I was applying the animation to so as not to have this happen.

While trying to get exception handling and ISRs to work, I had this happen to my bootsplash. I'm not quite sure what went wrong; at the time I was having exceptions occurring in the ISR handler and jumps to arbitrary locations in memory. As far as I could tell, this occurred during approximately the 10th ISR or so.

klange wrote:Working on animations in my compositor, and I accidentally told the background window to run the "map out" effect:



... I neglected to check which window I was applying the animation to so as not to have this happen.

Trippiest photo! Love it.