sprint f , we bring up its call graph node as well (by pressing the CGRAPH button at the bottom of the summary window). ... the programmer had removed some debugging print statements, but had inadvertently forgotten to delete an sprint f call that formatted strings containing debugging information. ... Clicking on the bar produced the source code window of Figure 32 with the lock of line 195 highlighted.
|Title||:||Multiprocessor performance debugging and memory bottlenecks|
|Author||:||A. J. Goldberg, Stanford University. Computer Science Dept|