understanding trace.log

Lutger lutger.blijdestijn at gmail.com
Tue Nov 21 09:02:58 PST 2006

Can someone enlighten me on the meaning of trace.log generated with 
-profile? I understand the basics of the call tree thing and timings, 
but look at this part:

	    2	_D8testbase7foobar1FZv
_D8testbase7foobar2FZv	2	433	433

Here, testbar.foobar1 (which calls testbase.foobar2) is called 2 times. 
But what do the 433 and 433 numbers mean?

Also, I'm not sure how to parse trace.log when multiple runs get merged, 
but perhaps I'll figure this out.

One last question for my curiosity: does helping the linker with 
trace.def work with D as is outlined in the C++ documentation?


More information about the Digitalmars-d-learn mailing list