Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Thu, 3 May 2001 17:41:26 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: DJ Please read - profiling Message-ID: <20010503174126.A7456@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <000801c0d415$96ccf4b0$0200a8c0 AT lifelesswks> <200105032130 DOT RAA03969 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <200105032130.RAA03969@envy.delorie.com>; from dj@delorie.com on Thu, May 03, 2001 at 05:30:30PM -0400 On Thu, May 03, 2001 at 05:30:30PM -0400, DJ Delorie wrote: >The next step is the profiler itself - you can use gprof, but the >granularity is pretty bad for quick-lived things like cygwin. I wrote >something that single-stepped the program using the debug API and built >a profile from that; you'd have to ask Chris if I can publish it, >assuming it still works. Sure, feel free to publish this. I was thinking about digging out my copy for this reason but I need to upgrade my system first. :-) cgf