Christopher Faylor wrote: > And that solves your problem, then? It appears to. The test is still running, but the stack is no longer walking through memory -- it is always using the same memory region for the pipe_read cygthread stack, as a matter of fact. Do you want a patch or will you take care of it? -- Joe Buehler