| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
init can just open `/tty` instead
|
|
|
|
|
|
|
|
|
|
|
|
this avoid accidental dereferences, and now it's easy to tell apart
which pointers are safe to directly read and which aren't.
cons:
- const is completely discarded
|
|
`()` means that any amt of arguments will be accepted, which isn't what
i want
|
|
|
|
|
|
|
|
|
|
|
|
|
|
it occureed if the path_simplify returned a negative value - instead of
being interpreter as an error it just carried on, ending up in an
infinite loop.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The length is a int, because the syscall will have a signed output. A
negative return value will mean an error (such as when it gets called
by a childless process).
|
|
well i guess it compiles now
|
|
|
|
|
|
|
|
|
|
I'm about to need that for waits(). There's no single list of processes
for simplicity's sake, but the search will now be even slower and it
might even introduce a potential vuln! How fun! Someone could override
stuff in .bss with random values. I'll either make gcc check if it
hasn't gone past the end of the stack, or turn this into a non recursive
function.
|
|
|
|
|
|
most syscalls will have to do this to copy memory around or whatever.
it's pretty ugly too, but i can't come up with a better abstraction...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
it's kinda bad. it passes the tests, though...
|
