Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Serious performance problems (malloc related?)
Date: Fri, 3 Jun 2005 12:16:39 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <42A02B68.4080707@exmsft.com>
Message-ID: <SERRANO4CxpAOAkK5Lq00000287@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Keith Moore
>Sent: 03 June 2005 11:05

> Christopher Faylor wrote:
> 
>> Keith, you don't have a complete reference for the Nt functions do you?
> 
> For the most part, using the APIs is pretty straight-forward if you have
> the required prototypes and structure definitions. With the possible
> exception of NtCreateProcess(), there is not a lot of "magic" involved.
> The MinGW project has done a lot of good work in this area. There also
> a ton of useful information in the MS DDK. The DDK is, obviously,
> focused on kernel-mode drivers, but much of the information is applicable
> to user-mode apps.
> 
> So, unfortunately, I don't have a complete reference, but there are
> enough "islands of information" around for us to piece together
> everything we need.


  I have a copy of Nebbett at home and a couple of years native api
experience, so I can always be leaned on to look stuff up and help out.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/