public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "KEREP, Mladen" <mladen.kerep@airbus.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Handles returned by mq_open are not valid file descriptors as supposed to be under native linux distributions
Date: Fri, 27 Mar 2015 11:44:00 -0000	[thread overview]
Message-ID: <556891A1F0F6154CB3DD7811A49431534D3B8027@FOWEXMC003.de.astrium.corp> (raw)

We're using POSIX message queues to pass messages between processes.
For this we've build a library layer to be able to use message queues on different platforms. Basically linux (debian, Ubuntu, archlinux, rasbian) is the development platform, but also vxworks platforms are supported.

Several message queues are opened through mq_open calls and the returned handles are organized in file descriptor sets (fd_set). The set is then passed over to a select(2) call, which blocks processing and returns as soon as any message in any of the queues arrives.

This works under linux, since the handles returned are valid file descriptors and the macros FD_ZERO / FD_SET are able to handle that handles.

However, under Cygwin, mq_open does not directly return file handles, but pointers to (unknown) data structures in memory (ref. http://sourceware.org/ml/cygwin/2013-07/msg00179.html), which cannot be used with FD_ZERO, FD_SET, so not with select(2). I know from the man pages (mq_open):
"Polling message queue descriptors
On Linux, a message queue descriptor is actually a file descriptor, and can be monitored using select(2), poll(2), or epoll(7).  This is not portable."

mq_open() and select() conform to POSIX.1-2001, at least under linux, but also under Cygwin ?
How can this be modified, so that it works under Cygwin as well ?

Here's a small code example, showing a segmentation fault in macros FD_ZERO/FD_SET:

#include <stdio.h>
#include <stdlib.h>
#include <mqueue.h>
#include <string.h>
#include <errno.h>
#include <fcntl.h>
#include <unistd.h>

int main(void)
{
  int res;
  int i = 0;
  char msgQueueTestName[] = "/testQueue";
  mqd_t testQueue;
  struct mq_attr  attrQueue;
  fd_set readfds;
  int highest_fd;
  int numMessages;

  memset(&attrQueue,0x00,sizeof(attrQueue));
  attrQueue.mq_maxmsg  = 10;  /* room for X messages in the queue */
  attrQueue.mq_msgsize = 20;  /* maximum size of a message */

  /* this example has only one message queue; usually several message queues are opened by different processes */
  testQueue = mq_open(msgQueueTestName, O_RDWR | O_CREAT, S_IRWXU | S_IRWXG, &attrQueue);
  if( testQueue == (mqd_t)-1 )
  {
      printf("Failed to open msg queue %s: %s %d\n", msgQueueTestName, sys_errlist[errno],errno);
  }
  else
  {
      printf("msg queue descriptor %d (0x%x)\n", testQueue, testQueue);
  }

  highest_fd = 0;

  /* here, usually we scan all opened message queues for highest fd */
  if (testQueue > highest_fd)
	highest_fd = testQueue;
  highest_fd++;
  printf("highest fd %d (0x%x)\n", highest_fd, highest_fd);

  /* add all file descriptors to be checked */
  FD_ZERO(&readfds);
  FD_SET(testQueue, &readfds);
  printf("readfds entries %d\n", sizeof(readfds.fds_bits) / sizeof(fd_mask));

  numMessages = select(highest_fd, &readfds, NULL, NULL, (struct timeval *) NULL);
  printf("messages pending %d\n", numMessages);


  return EXIT_SUCCESS;
}

Any help will be appreciated.
Mladen


--
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

             reply	other threads:[~2015-03-27  9:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 11:44 KEREP, Mladen [this message]
2015-03-30 13:33 ` Corinna Vinschen
     [not found] ` <6744_1427719032_55194377_6744_15232_1_20150330123643.GC10785@calimero.vinschen.de>
2015-03-30 14:54   ` KEREP, Mladen

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=556891A1F0F6154CB3DD7811A49431534D3B8027@FOWEXMC003.de.astrium.corp \
    --to=mladen.kerep@airbus.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).