2002/04/15 by Joseph R. Kiniry, Kiniry, Joseph R.
Computer Science · Decision Sciences · #Advanced Software Engineering Methodologies #D.2 #D.2.5 #FOS: Computer and information sciences #Scientific Computing and Data Management #Software Engineering (cs.SE) #Software Engineering Research #cs.SE
paper · pdf · doi:10.48550/arxiv.cs/0204034
12 pages, 3 figures, submitted to OOPSLA '02
arxiv created 2002/04/15 · openalex publication_date 2002/04/15 · arxiv updated 2009/11/30 · openalex created_date 2025/10/10 · openalex updated_date 2026/07/28
A major part of debugging, testing, and analyzing a complex software system is understanding what is happening within the system at run-time. Some developers advocate running within a debugger to better understand the system at this level. Others embed logging statements, even in the form of hard-coded calls to print functions, throughout the code. These techniques are all general, rough forms of what we call system monitoring, and, while they have limited usefulness in simple, sequential systems, they are nearly useless in complex, concurrent ones. We propose a set of new mechanisms, collectively known as a monitoring system, for understanding such complex systems, and we describe an example implementation of such a system, called IDebug, for the Java programming language.