This is the mail archive of the
mailing list for the Cygwin project.
Re: Fork and Windows Heap
- From: RenÃ Berber <rene dot berber at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 15 Jun 2016 21:48:43 -0500
- Subject: Re: Fork and Windows Heap
- Authentication-results: sourceware.org; auth=none
- References: <D38743FD dot 926E%billziss at navimatics dot com>
- Reply-to: Do not reply <rene dot berber at gmail dot com>
On 6/15/2016 7:42 PM, Bill Zissimopoulos wrote:
> WinFsp consists of an FSD (file system driver) and a DLL component. The
> WinFsp DLL uses the Windows heap functions to manage memory
> (HeapAlloc/HeapFree). It seems that the Windows heap is not properly
> cloned after a fork, which leads to the crash I am experiencing. I have
> the following questions:
> (1) Is my assumption that Windows heaps are not properly cloned after a
> fork correct? A 2011 post  seems to suggest so.
> (2) Is there any workaround that the WinFsp DLL can use to get around this
> limitation and work properly after a fork? The obvious answer would be to
> have the DLL use Cygwin's malloc/free and this is indeed possible within
> the DLL's FUSE layer, but not workable elsewhere.
Those are the wrong questions: you shouldn't be mixing Windows and Unix
(SuSv4, Posix) APIs, and by your description you are trying a Windows
port, mixing it with probably the base, and expecting it to work on
Cygwin, that's a no-go from the start.
Unix software usually requires no porting, or very little to account for
libc implementations (glibc in Linux, newlib in Cygwin), and the Windows
I think you have 2 options:
1. Keep the Windows port and use the cross-compiler tools to create
Windows native binaries. That means: forget about fork, start using the
spawn family of functions, i.e. _wspawnvp. Of course the result will
work independently of Cygwin, daemons are called services (and created
2. Keep the base Unix version for everything. Fork/exec works fine,
daemon works fine but you'll have to use cygrunsrv to install the daemon
You should read the documentation:
Hope this helps.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple