Update: Marc (distribution author) has fixed it in version 4.6, now the example works as expected, will test it more ("async file operations", rather than just "aio_utime") later.

Looks like async file operations are popular topic; I also was trying, recently, to replace what I'm using with something more elegant. However, async file copy (aio_copy) fails, at the step (see description) of changing file atime and mtime. So it can be reduced to failure of aio_utime.

use strict;
use warnings;
use feature 'say';

use AnyEvent;
use AnyEvent::IO;

my $c = AnyEvent-> condvar;
aio_utime( 'x', 0, 0, sub { $c-> send( @_ )});
say $c-> recv;
[download]

File named 'x' is in current directory, IO::AIO and AnyEvent::AIO should be installed. The above example works in Linux, but not in Windows (where actual script is to be used). Perl dies silently in Win10, or with usual OS messagebox "Application needs to be closed blah-blah" in e.g. Win2008.

I found that if this line is replaced with

int i;
printf( "calling\n" );
i = utime (filename, &buf);
printf( "called\n" );
return i;
[download]

then I only see "calling", and process crashes. A call to "utime" looks quite innocent, of course it works from either simple C program or wrapped into Perl and Inline::C. Apart from reporting a bug, perhaps there is some simple and quick fix?