[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 88520] pipe+fork+dup2 kills the main program
From:       Tom Hughes <thh () cyberscience ! com>
Date:       2004-08-31 21:27:59
Message-ID: 20040831212759.5143.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=88520      




------- Additional Comments From thh cyberscience com  2004-08-31 23:27 -------
So where does the pipe+fork+dup2 of the title come from? Is that from the real \
problem or from the "test case" program? Do we actually know that you need all those \
three elements to trigger the problem or might that be (in part at least) a red \
herring? It sounds like all you actually know is that a forked child is dieing  with \
a segmentation fault?

Is the child process being run under valgrind or not? ie are you using \
--trace-children=yes?

That signal trace is normal by the way - when the stack needs to grow a segmentation \
fault occurs which valgrind traps and uses to trigger the allocation of extra stack \
space.


[prev in list] [next in list] [prev in thread] [next in thread]