From:	craig AT reversion DOT ca (Craig Nelson)
Subject:	sockets and fork() under b18 coolview
23 Jan 1998 23:59:55 -0800 :
Message-ID:	<199701230030.RAA00648.cygnus.gnu-win32@tuffy.reversion.ca>
To:	gnu-win32 AT cygnus DOT com
Cc:	craig AT reversion DOT ca

I am having trouble with a socket request server under win95.

If I write a program to handle incoming socket requests, one at a time, the
program runs beautiful.  however, if I modify the program to use fork() to 
process each socket request, the program dumps, reporting that the stack is
probably corrupted.

I've tried to narrow the problem down using a small test case program, and that
also runs fine with, or without fork().  But using the original program under
every other unix works flawlessly as well (even purified).

My theory is this:  

	-Because the original program runs fine with unix, i will assume its ok.

	-Because the original program runs fine when used on gnu-win32 without
	 fork(), i will continue to assume that it's ok.

	-The smaller test program only worked because it did not "do enough"
	 other processing for the system to realize that the stack had been
	 corrupted.

And so I conclude that the problem is with fork() under gnu-win32.

Has anyone else experienced this scenario with fork?

I've checked all the archives, FAQs and everything, so this is my last resort.

I would certainly appreciate any help anyone has to offer..

Thanks,
Craig Nelson, Cameo Systems.

craig AT reversion DOT ca
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -