Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!news.iecc.com!nerds-end From: Michael Dunlavey Newsgroups: comp.compilers Subject: C++ runtime profiling Date: Fri, 13 Jan 2012 19:52:23 -0500 Organization: Compilers Central Lines: 12 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <12-01-018@comp.compilers> NNTP-Posting-Host: news.iecc.com X-Trace: leila.iecc.com 1326571888 86051 64.57.183.58 (14 Jan 2012 20:11:28 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Sat, 14 Jan 2012 20:11:28 +0000 (UTC) Keywords: C++, debug Posted-Date: 14 Jan 2012 15:11:28 EST X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: x330-a1.tempe.blueboxinc.net comp.compilers:417 I think the best tool for performance tuning isn't a tool at all, it's a technique - random pausing. Here's a sourceforge project that walks through a specific example: https://sourceforge.net/projects/randompausedemo/ Here is a list of objections to gprof and other profilers: http://stackoverflow.com/questions/1777556/alternatives-to-gprof/1779343#1779343 Mike Dunlavey Pharsight