From:	rob AT blairlake DOT com (Little Robbie Burcham)
Subject:	CYGWIN32 experts, please help.
27 Feb 1997 17:49:34 -0800 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<Pine.OSF.3.91.970227160756.26201B-100000.cygnus.gnu-win32@guppy.blairlake.com>
Mime-Version:	1.0
Original-To:	gnu-win32 <gnu-win32 AT cygnus DOT com>
In-Reply-To:	<199702250650.RAA05106@mundook.cs.mu.OZ.AU>
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

I have been monitoring this list for a short time, and I have already 
been impressed by the quality of responses I have seen.  I hope my 
questions yield no exception.

My questions deal with the situation of running multiple instances of a 
CYGWIN32 gcc compiled program.

Do CYGWIN32 compiled programs run the risk of delving into one anothers' 
memory, or other resources for that matter?  If one instance of a program 
allocates heap space, will another instance be prevented from allocating 
the same heap space?

What about blocking file I/O?  Is there anything to be wary of, or do the 
ANSI C raw open & flock standards hold?

What about sockets?  Same question as above.

Ah, and now for the reason I am asking :)  I have noticed that some 
simple programs hang when bash is open.  They operate nicely when there 
is no bash instance.  It makes me wonder if bash puts a lock on the 
CYGWIN32.DLL, or if perhaps bash puts a lock on heap allocation attempts 
on the part of CYGWIN32.DLL, or something odd like that.

Has anyone else noticed this?  Any idears?

_______________________________________________________________________________
Rob Burcham
Blairlake New Media			    "He's nuts!  Somebody grab him!"
104 West 42nd Street, Kansas City, MO 66111
http://robb.blairlake.com (sometimes)
rob AT blairlake DOT com - rob AT ukans DOT edu

-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -