When your OS goes crazy - Screenshots
Re: When your OS goes crazy - Screenshots
Something went wrong with my printf implementation...
- BrightLight
- Member
- Posts: 901
- Joined: Sat Dec 27, 2014 9:11 am
- Location: Maadi, Cairo, Egypt
- Contact:
Re: When your OS goes crazy - Screenshots
It's because I forgot one line of code:
Code: Select all
mov byte[is_program_running], 0
You know your OS is advanced when you stop using the Intel programming guide as a reference.
Re: When your OS goes crazy - Screenshots
Significant interleaving of serial port log messages whilst I was stress-testing the scheduler:
I should probably do something about that.
Regards,
John.
Code: Select all
vfmoLodfs./
tyggs.vf
es:r. Logmoengetr: dferenisoterng ins_messsfag .rmectagssaore ge y:loloop
op
voofstfs: ent ent: ererining messag Moge lunootp
m: esmosauntingg te loop
ysos.rootfs to /
Regards,
John.
- hgoel
- Member
- Posts: 89
- Joined: Sun Feb 09, 2014 7:11 pm
- Libera.chat IRC: hgoel
- Location: Within a meter of a computer
Re: When your OS goes crazy - Screenshots
Not really sure why this is happening, something to do with my double buffering implementation
EDIT: I eventually figured it out, main issue was the size of the kernel after including that wallpaper data as a header exported from GIMP, it'd go from 17kb to 8MB
EDIT2: Actually seems like the problem might be something deeper than that, everything is fine if I copy the translated GIMP output into an array first and then just copy that to the framebuffer.
EDIT3: Finally found the problem, buffer overflow because GIMPS macro assumes that data will only be read once.
EDIT: I eventually figured it out, main issue was the size of the kernel after including that wallpaper data as a header exported from GIMP, it'd go from 17kb to 8MB
EDIT2: Actually seems like the problem might be something deeper than that, everything is fine if I copy the translated GIMP output into an array first and then just copy that to the framebuffer.
EDIT3: Finally found the problem, buffer overflow because GIMPS macro assumes that data will only be read once.
"If the truth is a cruel mistress, than a lie must be a nice girl"
Working on Cardinal
Find me at [url=irc://chat.freenode.net:6697/Cardinal-OS]#Cardinal-OS[/url] on freenode!
Working on Cardinal
Find me at [url=irc://chat.freenode.net:6697/Cardinal-OS]#Cardinal-OS[/url] on freenode!
Re: When your OS goes crazy - Screenshots
I have this strange suspicion it didn't actually allocate a block....
- hgoel
- Member
- Posts: 89
- Joined: Sun Feb 09, 2014 7:11 pm
- Libera.chat IRC: hgoel
- Location: Within a meter of a computer
Re: When your OS goes crazy - Screenshots
Well, setup multithreading, AHC and EXT2 parsing since my last post so I was trying my hand at loading an image from disk, this is the spectacular close but not there yet outcome:
"If the truth is a cruel mistress, than a lie must be a nice girl"
Working on Cardinal
Find me at [url=irc://chat.freenode.net:6697/Cardinal-OS]#Cardinal-OS[/url] on freenode!
Working on Cardinal
Find me at [url=irc://chat.freenode.net:6697/Cardinal-OS]#Cardinal-OS[/url] on freenode!
Re: When your OS goes crazy - Screenshots
When I finally managed to compile my kernel from a year ago again:
Re: When your OS goes crazy - Screenshots
Editing console rendering code always goes wrong. Today the redraw logic (used for scrolling and such) only updated a fourth of the screen, while the normal single-character rendering code continued to work.
- Vercas
- Posts: 2
- Joined: Thu May 28, 2015 9:16 am
- Libera.chat IRC: Vercas
- Location: Manchester, UK
- Contact:
Re: When your OS goes crazy - Screenshots
This photo is a bit old, but it shows quite accurately what happens when you don't check the framebuffer type (pixels or chars) that GRUB gives you:
On the other hand, it means that I used the rest of the info correctly.
On the other hand, it means that I used the rest of the info correctly.
My main project is Beelzebub.
Re: When your OS goes crazy - Screenshots
I was adjusting my panic() routine to send NMIs to the other cores causing them to also dump stack traces.
as they all got the NMI at the same time they all dumped their stack traces at the same time, they got interleaved
Re: When your OS goes crazy - Screenshots
Hmm.. Looks fine.
Let's test out my new scroll() function
... fail
- Vercas
- Posts: 2
- Joined: Thu May 28, 2015 9:16 am
- Libera.chat IRC: Vercas
- Location: Manchester, UK
- Contact:
Re: When your OS goes crazy - Screenshots
A couple of days old, it's a test of my object allocator with SMP.
Unsynchronized serial output FTW.
My main project is Beelzebub.
Re: When your OS goes crazy - Screenshots
When something really went wrong:
Printing text when SUDDENLY interrupt arrives
Printing text when SUDDENLY interrupt arrives
- Attachments
-
- I try to print "Hello, it's me" when interrupt wants to show itself
- sss.png (7.39 KiB) Viewed 12076 times
Re: When your OS goes crazy - Screenshots
ThiHellos iHellos HelloHelloindeeHellod verHelloy fuHellonny
Re: When your OS goes crazy - Screenshots
bug in my printDec( ) caused an infinite loop, and also a cool gradient