This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Precise Calling Context Encoding
Sept.-Oct. 2012 (vol. 38 no. 5)
pp. 1160-1177
William N. Sumner, Purdue University, West Lafayette
Yunhui Zheng, Purdue University, West Lafayette
Dasarath Weeratunge, Purdue University, West Lafayette
Xiangyu Zhang, Purdue University, West Lafayette
Calling contexts (CCs) are very important for a wide range of applications such as profiling, debugging, and event logging. Most applications perform expensive stack walking to recover contexts. The resulting contexts are often explicitly represented as a sequence of call sites and hence are bulky. We propose a technique to encode the current calling context of any point during an execution. In particular, an acyclic call path is encoded into one number through only integer additions. Recursive call paths are divided into acyclic subsequences and encoded independently. We leverage stack depth in a safe way to optimize encoding: If a calling context can be safely and uniquely identified by its stack depth, we do not perform encoding. We propose an algorithm to seamlessly fuse encoding and stack depth-based identification. The algorithm is safe because different contexts are guaranteed to have different IDs. It also ensures contexts can be faithfully decoded. Our experiments show that our technique incurs negligible overhead (0-6.4 percent). For most medium-sized programs, it can encode all contexts with just one number. For large programs, we are able to encode most calling contexts to a few numbers. We also present our experience of applying context encoding to debugging crash-based failures.
Index Terms:
Context,Encoding,Instruments,Image edge detection,Runtime,Decoding,Software algorithms,call graph,Calling context,context sensitivity,profiling,path encoding,calling context encoding
Citation:
William N. Sumner, Yunhui Zheng, Dasarath Weeratunge, Xiangyu Zhang, "Precise Calling Context Encoding," IEEE Transactions on Software Engineering, vol. 38, no. 5, pp. 1160-1177, Sept.-Oct. 2012, doi:10.1109/TSE.2011.70
Usage of this product signifies your acceptance of the Terms of Use.