Multi-level Debugging for Interpreter Developers
Conventional debuggers require programmers to work on multiple levels of abstraction at once when inspecting call stacks or data. This demands considerable cognitive overhead and deep system knowledge of all implementation technologies involved. When developing an interpreter, programmers often create a dedicated debugger to have a higher-level perspective on the client-language; the resulting use of multiple debuggers at once leads to mental context switches and needs an elaborated method.
We present an integrated debugging tool in which interpreter developers define and select the levels of abstraction on which they focus. Our debugger provides them with an abstraction-specialized view. We consider both host-language and guest-language levels, since either may be levels of interest in a debugging session. We show how this separation into host-language levels can ease the debugging of applications through filtering call stacks and specializing call stack representation on levels.
Tue 15 Mar Times are displayed in time zone: Greenwich Mean Time : Belfast change
|14:00 - 14:05|
|14:05 - 14:40|
|A Lightweight Optimization Technique for Data Types à la Carte|
Hirotada KiriyamaTokyo Institute of Technology, Tomoyuki AotaniTokyo Institute of Technology, Japan, Hidehiko MasuharaTokyo Institute of TechnologyDOI
|14:40 - 15:00|
|Multi-level Debugging for Interpreter Developers|
Bastian KruckHasso Plattner Institute, Potsdam, Stefan LehmannHasso-Plattner-Institute, Potsdam, Christoph KesslerHasso Plattner Institute, Potsdam, Jakob Reschke, Tim FelgentreffHPI, Germany, Jens LinckeHasso Plattner Institute, Robert HirschfeldHPIDOI Pre-print Media Attached