tarfeef101
|
74156bfff5
confirmed, bug with argtesttest is with a2b, not a2a (assuming a2a is actually fixed, of course)
|
6 lat temu |
tarfeef101
|
55542e5358
fixed a2a crap
|
6 lat temu |
tarfeef101
|
4a78e046da
fuck piazza
|
6 lat temu |
tarfeef101
|
11fc2beeac
got execv mostly working... arg2 and argc are kinda off with argtestest
|
6 lat temu |
tarfeef101
|
8b37d7e1e7
tested uw-testbin/argtest with argument passing (no execv), and it works flawlessly. so issue must be with execv specific code as discussed before, but now we have also validated the functionality of the argument copying
|
6 lat temu |
tarfeef101
|
03416ba12a
seems that arg passing may be working after all, but the bad memory reference i get on hogparty is simply due to the execv base functionality not working. hogparty isn't supposed to use argv. perhaps i am not setting up the userspace pointers properly...
|
6 lat temu |
tarfeef101
|
b9192e35bf
believe argument passing in runprogram working, have base execv without agrs working. with args is still not great
|
6 lat temu |
tarfeef101
|
4c3717c727
have a building kernel, can run old tests, but cannot run new ones. execv clearly needs work
|
6 lat temu |
tarfeef101
|
8f2d17547d
started execv, not sure how caret.proj will do stuff, guess i'll find out when i repoen it.
|
6 lat temu |
tarfeef101
|
ab2a8632a3
new branch for a2b
|
6 lat temu |
Tareef Dedhar
|
9b74ba733d
Merge branch 'a2a' of tarfeef101/cs350 into master
|
6 lat temu |
tarfeef101
|
a76a6813f0
rebuilt user level programs as per guidelines pre-submission
|
6 lat temu |
tarfeef101
|
a680c9cb45
removing old code, missed 1 element of the processes array in init
|
6 lat temu |
tarfeef101
|
41d0d447bd
added a script for non-complete building. also, fixed sys exit. issue was not deleting children that are zombies when parents die. i do that now
|
6 lat temu |
tarfeef101
|
2c8fab64f4
using the proper palin test, i am passing. think my sleep is the issue, or according to piazza the sleep is exposing issues with address spaces which could be a fork issue.
|
6 lat temu |
tarfeef101
|
42307f5601
using proclock more
|
6 lat temu |
tarfeef101
|
a982f748c5
actually update retval in getpid
|
6 lat temu |
tarfeef101
|
0e648f4fd6
added another condition to thread to allow for threads to die if their process has exited but exists because it wants to be usable by family|
|
6 lat temu |
tarfeef101
|
10cc744117
commented out dupe pe code from proc.c that was done in sys_exit
|
6 lat temu |
tarfeef101
|
6146aaa5c4
onefork now runs properly. palin and widefork do not. changed exit to update child procs to point to NULL parents if the parent exits
|
6 lat temu |
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
|
6 lat temu |
tarfeef101
|
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
|
6 lat temu |
tarfeef101
|
a539b02dd1
no longer leak memory, processes should actually have a list of children now
|
6 lat temu |
tarfeef101
|
800751896b
i don't crash instantly anymore!
|
6 lat temu |
tarfeef101
|
7d97cb9768
cannot compile, error with passing a function pointer in fork
|
6 lat temu |
tarfeef101
|
05b59315b6
debugging proc.c at comilation, some typedef issues. also need to actually USE lists to put children into parent when forking
|
6 lat temu |
tarfeef101
|
6506f399b8
added lists to kernel config
|
6 lat temu |
tarfeef101
|
70ed7f87b4
added logic to get/remove PIDs on process creation and destruction
|
6 lat temu |
tarfeef101
|
c6f66f8d4f
implemented thread fork? kinda???
|
6 lat temu |
tarfeef101
|
1eeb77366e
started adding logic to use the new proc structs in creation/deletion. no tracking actually implemented, nor testing or validation of any code. at all
|
6 lat temu |