Help Logs Database

Undernet  |  EFnet  |  Quakenet  |  Freenode  |  Ircnet  |  Dalnet
Page: 1 2 3 4 5 6 7 8 9 10 11 12

<alphakiller> hehehe
<_hhh_> Iam confused
<_hhh_> if I make a mistake in tss protection everybody will be able to jump to any task
<_hhh_> they just push cs,eip,flags on stack and do iret from 3rd priviledge level
<_hhh_> and modify tasks backlink for sure :)
<_hhh_> that can be a big mistake I think
<geist> _hhh_: dont use hardware tasking and the problem goes away
<geist> also, you can't use iret from ring 3
<NoorulIslaam> anyone alive?
<NoorulIslaam> hello kyelewis
<mmiikkee12> i am...
<Kototama> o/
<NoorulIslaam> hows ur OS doing mmiikkee12
<NoorulIslaam> popcorn :)
<mmiikkee12> pretty well
<mmiikkee12> i'm converting to C++ now :P
<mmiikkee12> i don't like C
<NoorulIslaam> WTF
<NoorulIslaam> R U INSANE?
<kyelewis> heh
<kyelewis> doing the C++ thing does bring extra pain upon yourself
<NoorulIslaam> surely i wasnt that bad a teacher to u :P
<mmiikkee12> :P
<kyelewis> more than possible, just more painful ;)
<mmiikkee12> it's actually easier...
<NoorulIslaam> mmiikkee12 nooooooooooooooo
<NoorulIslaam> stick to C
<NoorulIslaam> trust me
<mmiikkee12> i backed up my old source just in case...
<mmiikkee12> but c seems easier
<mmiikkee12> *c++
<NoorulIslaam> why does it seem easier?
<NoorulIslaam> please explain
<mmiikkee12> it's c plus 1!
<mmiikkee12> :)
<NoorulIslaam> who brainwashed u
<mmiikkee12> uh... let's see...
<mmiikkee12> it's a lot closer to java (which i know)
<mmiikkee12> it's a lot easier to get text
<mmiikkee12> input
<NoorulIslaam> huh
<NoorulIslaam> for example?
<erik`> as far as it can be called a kernel
<NoorulIslaam> how is it easier to get text input in c++ that in c?
<mmiikkee12> for some reason typedef struct just doesn't appeal to me as easy :P
<mmiikkee12> cin >> input;
<NoorulIslaam> that wont work in ur kernel
<erik`> :)
<mmiikkee12> (yes, it does)
<NoorulIslaam> u dont have the standard c++ library there
<erik`> NoorulIslaam: you could implement it :)
<mmiikkee12> i have cin and cout implemented
<NoorulIslaam> erik` true
<NoorulIslaam> but thats more work than just writing a print() function
<erik`> agreed
<mmiikkee12> c++ is cooler :P
<NoorulIslaam> no, its not
<NoorulIslaam> its gonna bloat ur kernel
<mmiikkee12> so it's 5kb larger, so what?
<mmiikkee12> (yes, i checked - only 5kb
<NoorulIslaam> wait until u get into memory management :)
<Kototama> :)
<Kototama> mmiikkee12 : did you implement exception ?
<mmiikkee12> no
<mmiikkee12> bah
<mmiikkee12> kernel locked up
<NoorulIslaam> how? :)
<Kototama> for global variables you use ctord and dtors tricks ? is there another way to get it done ?
<mmiikkee12> yes, in a c file there are _main and _atexit functions
<NoorulIslaam> why do u need to use "tricks" for global vars?
<NoorulIslaam> arent they just allocated on .data or .bss
<mmiikkee12> no
<mmiikkee12> they need runtime support
<NoorulIslaam> then?
<NoorulIslaam> why?
<mmiikkee12> they're 'special' - heck, i don't know :P
<NoorulIslaam> if u dont know
<NoorulIslaam> dont use C++
<Kototama> it's because you have static constructor
<NoorulIslaam> hrm so?
<Kototama> u think u can just have your constructors in a normal .data section ?
<NoorulIslaam> they would be in the .text section
<NoorulIslaam> they are code
<Kototama> yes sorry,.text section
<NoorulIslaam> so whats the prob?
<sigusr1> http://www.invalidsoftware.net/os/?the_id=11
<NoorulIslaam> every kernel has a .text section
<NoorulIslaam> ah yes
<NoorulIslaam> the constructors of global vars need to be called upon kernel initialization
<NoorulIslaam> since thats when they are "in scope" so to speak
<Kototama> doing a kernel in c++ is perhaps not the smartest thing but you learn a lot on c++ ;)
<sigusr1> meh.
<dr_evil> doing a kernel in C++ sounds like a great idea to me
<NoorulIslaam> do a kernel in a language that u invented
<NoorulIslaam> :D
<NoorulIslaam> or try writing one in ruby


Return to osdev
or
Go to some related logs:

Sulten som en okse
beginner
hmm wow patch

Copyright © 2005 www.irclogs.ws. All rights reserved. » disclaimer » contact