|
From: Nicholas N. <nj...@cs...> - 2005-08-26 18:57:40
|
On Fri, 26 Aug 2005, Jeroen N. Witmond wrote: > I am not sure I understand. The parent should flush the buffer, and does, > as the text 'done.' is produced. The child is told to SIGQUIT (dump core > and terminate), and should die immediatelly. Why can't the child flush the buffer before dying? Maybe it flushes it immediately after the fork(). AIUI, there's a point at which the buffer must be flushed, but it can be legitimately flushed at any time prior to that. > Are you saying that the flushing of the child's buffer is an artifact > introduced by valgrind? ;-) I'm saying that things sometimes behave differently under Valgrind, but I think in this case the different behaviour is quite valid. N |