Jeff King <peff <at> peff.net> writes: > > I'm not sure what an actual SIGPIPE death looks like on Windows. There is no SIGPIPE death on Windows due to total absence of SIGPIPE. raise(unsupported int) just causes ugly "git.exe has stopped working" window and possibly ends up as SIGABT (I don't know how to check this). > What > happens if git is still writing data to the pager and the pager exits? > Does it receive a signal of some sort? I'm not sure what you mean, sorry. check_pipe properly detects pager exit. The problem is with the way it tries to die. > The point of the code in check_pipe is to simulate that death. So > whatever happens to git in that case is what we would want to happen > when we call raise(SIGPIPE). That's what I'm talking about. On Windows, you can't raise(SIGPIPE). You can only raise(Windows_supported_signal) where signal is one of: SIGABRT, SIGFPE, SIGILL, SIGINT, SIGSEGV, SIGTERM as MSDN tells us. > A possibly simpler option would be to just have the MSVC build skip the > raise() call, and do the exit(141) that comes just after. That is > probably close enough simulation of SIGPIPE death. Isn't raise(SIGTERM/SIGINT) good enough? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html