On 9/8/2011 6:52 PM, Christopher Faylor wrote:
As I said, on Linux, if you call pclose twice in succession you get a SEGV. I am comfortable with Cygwin's behavior especially since you seem to be seeing an actual program problem.
unlikely a octave issue as it SEGFAULT's only on cygwin, and all the other platforms are fine: Linux, BSD, Apple. I suspect more a borderline cygwin issue that octave is just hitting. But of course I could be wrong.
$ grep 'pipe:\[5\]' octave.strace 24 595 [main] sh 2840 fhandler_base::fixup_after_exec: here for '/dev/fd/pipe:[5]' 35 103396815 [main] octave-3.4.2 3664 fhandler_base::close: closing '/dev/fd/pipe:[5]' handle 0x46C 37 896 [main] gs 2840 fhandler_base::fixup_after_exec: here for '/dev/fd/pipe:[5]' 48 93072 [main] sh 2840! fhandler_base::close: closing '/dev/fd/pipe:[5]' handle 0x46C 31 2358333 [main] gs 2840 fhandler_base::close: closing '/dev/fd/pipe:[5]' handle 0x46C but I guess they are the two sides of the pipeWell, one of them is in an execed process. Some of the others are in different processes. cgf
I will further look Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
