#64: atf-run gets stuck with huge outputs on stderr

["atf trac notification" <nobody%julipedia.org@localhost>]

#64: atf-run gets stuck with huge outputs on stderr
----------------------+-----------------------------------------------------
 Reporter:  jmmv      |       Owner:  jmmv
     Type:  defect    |      Status:  new 
 Priority:  critical  |   Milestone:  0.11
Component:  atf-run   |     Version:      
 Keywords:            |  
----------------------+-----------------------------------------------------
 As reported by Antti Kantee, a test case that generates "lots" of output
 on stderr hangs atf-run.

 An early diagnosis of the problem is as follows: atf-run poll(2)s for
 stdout and stderr of the child process and, when data is available,
 attempts to read a whole line of text from them. However, it *blindly*
 assumes that a line of text, ending by \n, is available.

 This is obviously wrong, because there is nothing that implies that when
 poll(2) says that data is available for read, a line of text will be
 available. And this is easier to trigger by writing to stderr than by
 writing to stdout because stderr is unbuffered.

 This requires some code slaying to remove useless abstractions, which will
 make the whole algorithm way simpler and more robust.

-- 
Ticket URL: <http://www.julipedia.org/projects/atf/trac/ticket/64>
Automated Testing Framework <http://www.NetBSD.org/~jmmv/atf/>
Automated Testing Framework