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 code is attempting to create the fifo in an unacceptable place
under Cygwin - I forget the directory it is trying to use.
for what I see it write in two places
under /dev/shm where it leave some trace
$ ls -l /dev/shm/
total 33M
-rw------- 1 Marco Kein 4.1M Feb 3 22:01
vader_segment.LAPTOP-82F08ILC.45860001.0
-rw------- 1 Marco Kein 4.1M Feb 3 22:01
vader_segment.LAPTOP-82F08ILC.45860001.1
-rw------- 1 Marco Kein 4.1M Feb 3 22:01
vader_segment.LAPTOP-82F08ILC.45860001.2
-rw------- 1 Marco Kein 4.1M Feb 3 22:01
vader_segment.LAPTOP-82F08ILC.45860001.3
-rw------- 1 Marco Kein 4.1M Feb 3 22:02
vader_segment.LAPTOP-82F08ILC.45a60001.0
-rw------- 1 Marco Kein 4.1M Feb 3 22:02
vader_segment.LAPTOP-82F08ILC.45a60001.1
-rw------- 1 Marco Kein 4.1M Feb 3 22:02
vader_segment.LAPTOP-82F08ILC.45a60001.2
-rw------- 1 Marco Kein 4.1M Feb 3 22:02
vader_segment.LAPTOP-82F08ILC.45a60001.3
and under /tmp/ompi.LAPTOP-82F08ILC.197609
as /tmp/ompi.LAPTOP-82F08ILC.197609/pid.93/0/debugger_attach_fifo
where at the end nothing remain under /tmp
The only thing strange I see is some tentative access to /proc/elog
that does not exist in Cygwin
