If a readpst child process fails with a nonzero status code for
whatever reason (killed, segfault, out-of-memory, ...) the parent
process will continue and likely end up exiting with status 0,
tricking the caller into thinking readpst was successful when it was
not.
http:// hg.five- ten-sg. com/libpst/ rev/6abc3054cba 2 in 0.6.67 must probably fix this:
libpst
changeset 358:6abc3054cba2
From Jeffrey Morlan:
If a readpst child process fails with a nonzero status code for
whatever reason (killed, segfault, out-of-memory, ...) the parent
process will continue and likely end up exiting with status 0,
tricking the caller into thinking readpst was successful when it was
not.