Wait syscall

[William Francis Cladek]

When I try to run either b.exe, long.exe, or null.exe from the shell, then
don't run properly and I see the same odd string on a new line, follwed
by the $ prompt as shown here:
[1;36m$

I figured out this happens right after my Wait syscall is called. It
seems that when I call Lookup_Thread with the passed pid, it is always
returning NULL as the kthread pointer. Any ideas why this might be
happening?

Will

[William Francis Cladek]

Scratch that. The reason, it seems, was because my thread was not
properly set up and wasn't added to the list of threads, for whatever
reason.

Carry on.

Post by William Francis Cladek
When I try to run either b.exe, long.exe, or null.exe from the shell, then
don't run properly and I see the same odd string on a new line, follwed
[1;36m$
I figured out this happens right after my Wait syscall is called. It
seems that when I call Lookup_Thread with the passed pid, it is always
returning NULL as the kthread pointer. Any ideas why this might be
happening?
Will

[c***@CSIC.UMD.EDU]

Did you ever figure out why your thread lookup returned null
bcause that the error that I am getting?
Jeff

[William Francis Cladek]

Yeah, when you called Start_User_Program, you have to give a bool value
for "detached". It's never really defined what that is, but when I passed
it one thing (I forget which) it was not adding it to the kernel thread
list and thus it couldn't find the pid.

Will

Post by c***@CSIC.UMD.EDU
Did you ever figure out why your thread lookup returned null
bcause that the error that I am getting?
Jeff