On Fri, Mar 4, 2011 at 8:09 AM, Cristian Greco <[email protected]> wrote:
> Hi,
>
> this should fix a regression in kill05.
>
> Why did tst_resm/tst_exit get replaced by perror/exit in 84f181fd?
Because it's a child process and child processes should _not_ use
libltp for sanity and to avoid introducing determinism, test bugs, and
for cluttering up output (remember: you have to communicate to the
user which process is actually doing the work, they're sharing file
descriptors potentially, etc).
The proposed fix doesn't make sense though because do_master_child
always exits when the flow is executed correctly (i.e. there aren't
any early return statements from do_master_child, etc. Is it not
resuming the stack appropriately after it gets signaled? What's the
call flow exactly for the failure?
Thanks,
-Garrett
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
