gprof profiling of multi-threaded Cygwin programs

Mark Geisert
Thu Feb 18 06:36:00 GMT 2016

On Wed, 17 Feb 2016, Corinna Vinschen wrote:
> Hi Mark,
> thanks for the patch.  Generally the patch is fine, I have just a few
> nits.
> On Feb 16 21:28, Mark Geisert wrote:
>> I've attached a patch set modifying Cygwin's profiling support to sample PC
>> values of all an application's threads, not just the main thread.  There is
>> no change to how profiling is requested: just compile and link the app with
>> "-pg" as usual.  The profiling info is dumped into file gmon.out as usual.
>> There is a behavioral change that ought to be documented somewhere:  If a
> If it ought to be documented, what about providing the doc patch, too?
> Any chance you could come up with a short section about profiling in the
> context of winsup/doc/programming.xml?  Otherwise there's basically only
> the description of the ssp tool in winsup/doc/utils.xml yet, which is a
> bit ... disappointing.

I can provide a doc patch but I could not figure out where this behavior 
change should be documented.  winsup/doc/utils.xml is concerned with tools 
written for Cygwin, but the behavior change is to bog-standard gprof from 
binutils that we're using on Cygwin.  (Note that no gprof code was 
changed; it's the system that's changed under it.)  There is no 
/usr/share/doc/Cygwin/binutils.README yet and I guess that's because there 
hasn't been a need for one.  Not sure this qualifies.

It seems like a Cygwin-specific gprof man page patch is what's called for. 
Is there an example of that in the source tree I could crib from?

I do see that a case could be made for general profiling documentation in 
winsup/doc/programming.xml but that's more than I want to take on at the 

All your other review comments are OK by me and I'll implement those and 
resubmit the patch when that's done, including the simple doc update.
Thanks much,


More information about the Cygwin-patches mailing list