Chapter 4 - DSpace at Waseda University

Chapter 4
ways of debugging according to the level and features of the problems. While there are some
problems which ask for a lot of time to analyze the problems. On the other hand, there are
also problems which can be debugged simply. However, most of the real projects do not
include simple problems. Therefore, the important issue here is that how to solve the problem.
� Reproduction of problematic situation
In order to solve the problem, it is important to be well aware of the way to
reproduce the problem. How the error occurs and how it causes the systemic
problems are very vital. However, the problems occurred from an embedded
system varies from the simple problem resulted from the error of one source code
to the complicated problems which are accumulated by each of single problems
causing butterfly effect. For instances, in case of embedded Linux OS, although the
memory leak problem does not have any problems during the short term period test,
it might occur in long, repeated time test. In this situation, it is hard to link cause
and result unless creation of memory leak is checked. If a program is written to be
locked after giving 1Kbyte to function in device driver, it would take long time for
a system to stop due to memory lack. Therefore, how fast it can be replayed is a
good stepping-stone for debugging.
� Understanding of a problem clearly.
By working with various engineers it is possible to see many features of
engineers. Some developers concentrated in ‘Copy & Paste’, too sensitive that
lines up space of program line, and a fast developer, etc. Among these developers,
it is one who knows specific details about created codes that have a highest ability
40