Abstract
Despite the best efforts of software engineers to produce high-quality software, inevitably some bugs escape even the most rigorous testing process and are first encountered by end users. When this happens, such failures must be understood quickly, the underlying bugs fixed, and deployments patched to avoid another user (or the same one) running into the same problem again. As far back as 1951, the dawn of modern computing, Stanley Gill wrote that "some attention has, therefore, been given to the problem of dealing with mistakes after the programme has been tried and found to fail." Gill went on to describe the first use of "the post-mortem technique" in software, whereby the running program was modified to record important system state as it ran so that the programmer could later understand what happened and why the software failed.
Publisher
Association for Computing Machinery (ACM)
Reference11 articles.
1. Bash Reference Manual. 2009. https://www.gnu.org/s/bash/manual/bash.html. Bash Reference Manual. 2009. https://www.gnu.org/s/bash/manual/bash.html.
2. Debugging with ruby-debug. 2011; http://bashdb.sourceforge.net/ruby-debug.html#Post_002dMortem-Debugging. Debugging with ruby-debug. 2011; http://bashdb.sourceforge.net/ruby-debug.html#Post_002dMortem-Debugging.
3. Erlang Runtime System Application User's Guide version 5.8.4. 2011. How to interpret the Erlangcrash dumps; http://www.erlang.org/doc/apps/erts/crash_dump.html. Erlang Runtime System Application User's Guide version 5.8.4. 2011. How to interpret the Erlangcrash dumps; http://www.erlang.org/doc/apps/erts/crash_dump.html.
Cited by
1 articles.
订阅此论文施引文献
订阅此论文施引文献，注册后可以免费订阅5篇论文的施引文献，订阅后可以查看论文全部施引文献
1. Hot Code Patching in CPython;Proceedings of the 14th Workshop on Implementation, Compilation, Optimization of Object-Oriented Languages, Programs and Systems - ICOOOLPS '19;2019