Debugging with Back-In-Time Evaluation
In the current state of debugging, there are bugs which exceed the capabilities of conventional online debuggers. When developers have to inspect past states of programs in order to solve them, they often have to restart the applications to be able to analyze the states live instead of inspecting them retrospectively. Omniscient debugging offers back-in-time debugging capabilities by recording full runs of applications, at the cost of scalability.
In this work we present an in-between approach called back-in-time evaluation that extends online debuggers with back-in-time capabilities. Instead of tracing full runs, the lifetime of the stored events are reduced to the scope of the methods they are executed in, which incurs a runtime overhead of only a few percent.
|Extended Abstract (morevms17-paper10.pdf)||150KiB|
Mon 3 Apr Times are displayed in time zone: Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna change
09:00 - 10:30
|When a Mouse Eats a Python: Smalltalk-style Development for Python and Ruby|
Tim FelgentreffHasso-Plattner-Institute, Potsdam, Fabio NiephausHasso Plattner Institute, University of Potsdam, Tobias PapeHPI, Germany, Robert HirschfeldHPIFile Attached
|Debugging Await in Dart|
|Building Reusable, Low-overhead Tooling Support into a High Performance Polyglot VM|
Michael Van De VanterOracle LabsFile Attached
|Debugging with Back-In-Time Evaluation|