delorie.com/archives/browse.cgi | search |
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 |
Message-ID: | <BAY101-DAV292186B2F865770344A9180F70@phx.gbl> |
X-Originating-Email: | [d2walter AT hotmail DOT com] |
X-Sender: | d2walter AT hotmail DOT com |
From: | "Daniel Walter" <d2walter AT hotmail DOT com> |
To: | <cygwin AT cygwin DOT com> |
Subject: | profiling |
Date: | Sat, 18 Jun 2005 11:08:57 -0400 |
MIME-Version: | 1.0 |
Are there any profilers that can be used with cygwin that can trace the call stack every time they take a sample? gprof is not very useful for problems that involve overcalling optimized functions. -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |