From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: openmpi warning "unable to open debugger attach fifo"
Date: Mon, 27 Jan 2020 21:36:00 -0000 [thread overview]
Message-ID: <9ef4f74e-3ee6-fef9-1fe7-d861cf7c6f04@gmail.com> (raw)
In-Reply-To: <a7942e52-5e80-e3fd-ad37-c1292dab99c1@cornell.edu>
Am 27.01.2020 um 22:28 schrieb Ken Brown:
> On 1/27/2020 1:49 PM, Ken Brown wrote:
>> On 1/27/2020 11:41 AM, Satish Balay wrote:
>>> Hi,
>>>
>>> On using openmpi from cygwin - I'm getting the following warning. Any idea how to avoid this?
>>>
>>>>>>>>>
>>> balay@ps5 ~
>>> $ /usr/bin/mpiexec -n 1 hostname
>>> ps5
>>> [ps5:00491] [[23611,0],0] unable to open debugger attach fifo
>>
>> The attempt to open a FIFO in the source file orte/orted/orted_submit.c:2862 is
>> failing due to a Cygwin bug. I think I see how to fix it. Stay tuned.
>
> Sorry, I spoke too soon and was misinterpreting some code I was reading. I
> don't see a Cygwin bug after all. Moreover, if I run your command under gdb, I
> don't get an error.
>
> Ken
>
I will look if the release candidate for 3.1.6 has still that issue.
3.1.5 had another larger warning that I silenced and that was due
to an upstream bug that has been solved.
This warning passed below my radar after I solved the bigger one.
Unfortunately OpenMPI takes age to build so do not expect any
too early..
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2020-01-27 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 16:41 Satish Balay
2020-01-27 18:49 ` Ken Brown
2020-01-27 21:28 ` Ken Brown
2020-01-27 21:36 ` Marco Atzeri [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9ef4f74e-3ee6-fef9-1fe7-d861cf7c6f04@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).