On Jul 31 18:00, Ken Brown wrote: > On 7/31/2019 11:53 AM, Ken Brown wrote: > > On 7/29/2019 2:55 PM, Ken Brown wrote: > >> Here's the error that I can reproduce easily in xterm: > >> > >> $ ls <(grep bash .bashrc) > >> /dev/fd/63 > >> grep: write error: Broken pipe > >>[...] > > [...] > > 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. For > example, here's what I see when I launch mintty from xwin-xdg-menu: > > $ pgrep mintty > 5375 > > $ ls -l /proc/5375/fd > total 0 > lrwxrwxrwx 1 kbrown None 0 2019-07-31 13:37 0 -> /dev/null > lrwxrwxrwx 1 kbrown None 0 2019-07-31 13:37 1 -> pipe:[38654736160] > lrwxrwxrwx 1 kbrown None 0 2019-07-31 13:37 2 -> pipe:[42949703456] > lrwxrwxrwx 1 kbrown None 0 2019-07-31 13:37 3 -> /dev/ptmx > lrwxrwxrwx 1 kbrown None 0 2019-07-31 13:37 4 -> /dev/windows > > These pipes are apparently used for logging. > > I don't see how this would explain my observations (grep reporting a broken > pipe), but it is at least a difference between a terminal started from > xwin-xdg-menu and an "ordinary" terminal. > > Anyway, I don't see any evidence here of a Cygwin bug.
I'm glad to read that :) Corinna -- Corinna Vinschen Cygwin Maintainer
signature.asc
Description: PGP signature
