From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: what does this cygserver error mean?
Date: Mon, 18 Apr 2011 19:46:00 -0000 [thread overview]
Message-ID: <20110418192600.GI25815@calimero.vinschen.de> (raw)
In-Reply-To: <201104181334.02386.icanprogram@295.ca>
On Apr 18 13:34, bob 295 wrote:
> (I'm in digest mode on this list so I can't thread my response easily.)
>
> The cygserver is setup to run as a Windows service. As far as I can tell the
> cygserver is running when the error occurs. What isn't clear from your
> response is what causes the named pipe to cygserver to get created? What
> tears it down?
Every single request to cygserver is basically a closed operation.
A function call like shmget opens the pipe, writes a request block,
reads the reply from cygserver and closes the pipe.
>
> In my test the sequence of each Send/Receive/Reply message pass involves these
> steps:
> 1) the sender creates the shared memory and then attaches to for the purpose
> of writing a message.
> 2) The receiver gets passed the shmid (via a named pipe) and attaches for the
> purpose of reading the message.
> 3) The receiver will respond by writing into same shared memory area upon
> which it will detach.
Wouldn't it be simpler to use POSIX shared memory for that? shm_open
allows to specify a named shared memory which all applications of a
project can share without having to use IPC to transmit the name (aka
"shmid") of the shared region. On Cygwin it also drops the requirement
to use cygserver.
> I have a script which is repeatedly sending a 1k message (up to 10 times).
> The error isn't consistently happening but when it does it appears to happen
> on the first message pass.
If you could create a very simple, self-contained testscase in plain C,
I'd take a look.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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
next prev parent reply other threads:[~2011-04-18 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 19:27 bob 295
2011-04-18 19:46 ` Corinna Vinschen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-16 3:41 bob 295
2011-04-18 12:23 ` Corinna Vinschen
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=20110418192600.GI25815@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).