| .. |
|
arch
|
800751896b
i don't crash instantly anymore!
|
il y a 6 ans |
|
compile
|
b6ecc99a2f
made the onefork test finish by changing the >= 0 to != -1, but this is a bandaid fix. the core issue of our exitcode being DEADBEEF still exists
|
il y a 6 ans |
|
conf
|
6506f399b8
added lists to kernel config
|
il y a 6 ans |
|
dev
|
731461ebee
initial commit, after a0 completion
|
il y a 7 ans |
|
fs
|
731461ebee
initial commit, after a0 completion
|
il y a 7 ans |
|
include
|
2a4d22c8a4
NOT WORKING: as all the printfs would tell you. basically, the palin test is trying to exit from a null or kernel thread, and the onefork test hangs. this is because a seemingly valid parent address has a DEADBEEF exitcode, which makes us skip the deletion of our thread
|
il y a 6 ans |
|
lib
|
05b59315b6
debugging proc.c at comilation, some typedef issues. also need to actually USE lists to put children into parent when forking
|
il y a 6 ans |
|
proc
|
2a4d22c8a4
NOT WORKING: as all the printfs would tell you. basically, the palin test is trying to exit from a null or kernel thread, and the onefork test hangs. this is because a seemingly valid parent address has a DEADBEEF exitcode, which makes us skip the deletion of our thread
|
il y a 6 ans |
|
startup
|
731461ebee
initial commit, after a0 completion
|
il y a 7 ans |
|
synchprobs
|
ebdc6909c9
moving back to working copy
|
il y a 6 ans |
|
syscall
|
b6ecc99a2f
made the onefork test finish by changing the >= 0 to != -1, but this is a bandaid fix. the core issue of our exitcode being DEADBEEF still exists
|
il y a 6 ans |
|
test
|
731461ebee
initial commit, after a0 completion
|
il y a 7 ans |
|
thread
|
2287d4f1c9
more formatting changes
|
il y a 6 ans |
|
vfs
|
731461ebee
initial commit, after a0 completion
|
il y a 7 ans |
|
vm
|
731461ebee
initial commit, after a0 completion
|
il y a 7 ans |
|
Makefile
|
731461ebee
initial commit, after a0 completion
|
il y a 7 ans |
|
build
|
e164117860
adding built kernel files,more formatting
|
il y a 6 ans |
tarfeef101
b6ecc99a2f
made the onefork test finish by changing the >= 0 to != -1, but this is a bandaid fix. the core issue of our exitcode being DEADBEEF still exists