delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1997/01/21/19:09:54

From: dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Subject: Re: cygwin b17.1 system() using inefficient fork() instead of true
vfork()
21 Jan 1997 19:09:54 -0800 :
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <009AEB8D.875742C0.7834.cygnus.gnu-win32@ifk20.mach.uni-karlsruhe.de>
Original-To: pcollins AT best DOT com
Original-CC: gnu-win32 AT cygnus DOT com, dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Hi, you wrote:

: If you are doing a lot of malloc calls on NT you should check out
: smartheap by Microquill. [...] See www.microquill.com.

Thanks, I'll have a look at it. [browsing a while]
Not cheap, IMHO, but it seems in our case there are at least no royalties.

Although my point was performance of forking large processes,
I hope smartheap will work and not make it worse.
Could there be problems with gcc/gdb/cygwin32 on NT?
So far I only used the standard (read: no cost) calloc on unix.


Bye, Heribert (dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de)
-
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 -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019