Discussion:
Forktest Question
(too old to reply)
Evgeny
2011-07-22 03:55:00 UTC
Permalink
Hi,

We are testing forktest after implementing on-demand page loading and
notice the following output:

testbin/forktest: Starting.
0123testbin/forktest: pid 5: exit -559038737
testbin/forktest: pid 4: exit -559038737

testbin/forktest: Complete.
Operation took 0.523906880 seconds

The test doesn't fail (at the end it reports as complete), but we are
concerned that some child process exited with bad exit codes. Also,
forktest worked perfectly well in our A2.

Could you please let us know if the above output is considered as a
successful test or a fail? In case of a fail, what could cause this?

Thank you!
cs350
2011-07-22 07:00:01 UTC
Permalink
As a general guideline, your kernel should execute each program correctly
and produce plausible vm statistics. You can also lose points for things
like having debug output (probably depending on how disruptive it is).

I don't think forktest returns negative codes.

Also it looks like -559038737 is the code, so the string of digits
produced by fork is just 0123, which is too short.

-Alex
Hi,
We are testing forktest after implementing on-demand page loading and notice
testbin/forktest: Starting.
0123testbin/forktest: pid 5: exit -559038737
testbin/forktest: pid 4: exit -559038737
testbin/forktest: Complete.
Operation took 0.523906880 seconds
The test doesn't fail (at the end it reports as complete), but we are
concerned that some child process exited with bad exit codes. Also, forktest
worked perfectly well in our A2.
Could you please let us know if the above output is considered as a
successful test or a fail? In case of a fail, what could cause this?
Thank you!
Ben Langmuir
2011-07-22 13:35:37 UTC
Permalink
Look at the source code for forktest: it only prints exit codes if they
aren't 0 (which they should be). It seems likely that the child
processes are being killed by the kernel after doing something illegal.

Ben
Post by Evgeny
Hi,
We are testing forktest after implementing on-demand page loading and
testbin/forktest: Starting.
0123testbin/forktest: pid 5: exit -559038737
testbin/forktest: pid 4: exit -559038737
testbin/forktest: Complete.
Operation took 0.523906880 seconds
The test doesn't fail (at the end it reports as complete), but we are
concerned that some child process exited with bad exit codes. Also,
forktest worked perfectly well in our A2.
Could you please let us know if the above output is considered as a
successful test or a fail? In case of a fail, what could cause this?
Thank you!
Loading...