This is the mail archive of the cygwin@sourceware.cygnus.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

CYGWIN32 experts, please help.


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@blairlake.com - rob@ukans.edu

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]