Regression (last snapshot)
Thu Aug 1 16:04:00 GMT 2019
On Aug 1 10:38, Eric Blake wrote:
> On 8/1/19 10:30 AM, Ken Brown wrote:
> >>> OK, when xwin-xdg-menu launches an application, it creates two pipes
> >>> and sets
> >>> the application's stdout and stderr to the write ends of those pipes.
> > Well, I can't be sure that the pipes are responsible. It's just that
> > the existence of the pipes is the only difference I could spot between
> > an ordinary terminal and a terminal started from xwin-xdg-menu.
> > Is it possible that the logging somehow slows things down or changes the
> > buffering, so that the grep process takes longer to complete? This
> > would be consistent with my theory that the broken pipe error doesn't
> > really represent a bug, but rather it reflects the fact that ls exits
> > before grep has finished writing.
> Could it be a case of xwin-xdg-menu calling signal(SIGPIPE, SIG_IGN) or
> similar, and accidentally letting grep inherit the ignored SIGPIPE?
execve doesn't propagate the signal dispositions, they get reset to
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: not available
More information about the Cygwin