> The process had finished, and that was why I was puzzled.
But had the process perhaps started some child process that had
(unintentionally) inherited the file handle, and that child process
was still running?
Please install Process Explorer from sysinternals.com and use its
"Find>Find Handle or
does, in fact work
pefectly on both platforms, so my problem lay elsewhere.
Richard
> (actually i don't know if this have the 'locking effect'), and you may
> interest using a GIOChannel for file operations.
>
> --- ajhwb
>
>
> --- richard.sh...@virgin.net wrot
close() your file
before exit (actually i don't know if this have the 'locking effect'), and you
may interest using a GIOChannel for file operations.
--- ajhwb
--- richard.sh...@virgin.net wrote:
From: Richard Shann
To: gtk-app-devel-list@gnome.org
Subject: Re: g_spawn and fi
On Mon, 2009-04-27 at 12:52 +0300, Tor Lillqvist wrote:
> > My application invokes the lilypond program using the g_spawn...
> > functions. This works fine on linux, but on windows the files created by
> > lilypond are left locked when lilypond has exited.
>
> That sounds very odd and in fact impo
> My application invokes the lilypond program using the g_spawn...
> functions. This works fine on linux, but on windows the files created by
> lilypond are left locked when lilypond has exited.
That sounds very odd and in fact impossible. Are you confusing file
protection with locking?
Please fi
My application invokes the lilypond program using the g_spawn...
functions. This works fine on linux, but on windows the files created by
lilypond are left locked when lilypond has exited. I can't re-use them
on the next invocation, for example.
Should I be exploring this as a possible bug in lilyp
