Re: [OMPI devel] 3.1.6rc2: Cygwin fifo warning

2020-02-03 Thread Marco Atzeri via devel
It seems a wrong count or a lost race, it is checking too late and the file and the /tmp/ompi.LAPTOP-82F08ILC.197609 tree is already close and gone 315 30730897 [main] orterun 93 close: close(21) 310 30731207 [main] orterun 93 fhandler_base::close: closing '/tmp/ompi.LAPTOP-82F08ILC.197609

Re: [OMPI devel] 3.1.6rc2: Cygwin fifo warning

2020-02-03 Thread Ralph Castain via devel
It is the latter one it is complaining about: > /tmp/ompi.LAPTOP-82F08ILC.197609/pid.93/0/debugger_attach_fifo I have no idea why it is complaining. > On Feb 3, 2020, at 2:03 PM, Marco Atzeri via devel > wrote: > > Am 03.02.2020 um 18:15 schrieb Ralph Castain via devel: >> Hi Marco >> mpirun

Re: [OMPI devel] 3.1.6rc2: Cygwin fifo warning

2020-02-03 Thread Marco Atzeri via devel
Am 03.02.2020 um 18:15 schrieb Ralph Castain via devel: Hi Marco mpirun isn't trying to run a debugger. It is opening a fifo pipe in case a debugger later wishes to attach to the running job - it is used by an MPIR-based debugger to let mpirun know that it is attaching. My guess is that the c

Re: [OMPI devel] 3.1.6rc2: Cygwin fifo warning

2020-02-03 Thread Ralph Castain via devel
Hi Marco mpirun isn't trying to run a debugger. It is opening a fifo pipe in case a debugger later wishes to attach to the running job - it is used by an MPIR-based debugger to let mpirun know that it is attaching. My guess is that the code is attempting to create the fifo in an unacceptable pl