On Mon, Jan 22, 2007 at 01:12:44PM -0800, Michael G Schwern <[EMAIL PROTECTED]> 
wrote:
> Marc Lehmann wrote:
> > would it be possible to find out what the mmap arguments are and why it
> > fails?
> 
>      void * mmap(void *addr, size_t len, int prot, int flags, int fd, off_t 
> offset);

Uh, the arguments, not the parameters, the parameters obviously are ok, but
the actual arguments it complains about.

Unix mandates EINVAL for the length parameter being too large in which
case you might need to confgiure a smaller stackspace.

I guess not much I cna do about limittaions in OSX, so if a smaller stack
does not help, the only option would be an malloc fallback. But there is
really no reason why one couldn't mmap a megabyte or so on osx :/

> I altered Coro/Makefile.PL so it did not add -DHAVE_MMAP to $DEFINE and that 
> fixed things.

This should probably reported to your vendor, though. The osx manpage you
found clearly says this about EINVAL for mmap:

   [EINVAL]           MAP_FIXED was specified and the parameter was not page
                           aligned.  fd did not reference a regular or character
                           special file.

Coro/State.xs does neither.

-- 
                The choice of a
      -----==-     _GNU_
      ----==-- _       generation     Marc Lehmann
      ---==---(_)__  __ ____  __      [EMAIL PROTECTED]
      --==---/ / _ \/ // /\ \/ /      http://schmorp.de/
      -=====/_/_//_/\_,_/ /_/\_\      XX11-RIPE

Reply via email to