Lesson plan
Debugging information
Debugging information is information that describes a correspondence of elements in the source code, such as the names of variables and routines, to entities in the object code, which is found in an object file, such as a shared library or an executable. This kind of information allows a symbolic debugger to provide more a debugging experience that corresponds more closely to the source code. The debugging information may be compiled together with the module's binary file, or distributed in a separate file, or simply discarded during the compilation and/or linking. Because historically such information was associated with the symbol table (which originally was for the translation from exported identifier names to locations in the object file), they also commonly known as debug symbols. However, most debug information today exists outside of the symbol table, making this largely a misnomer. This information can be helpful while trying to investigate and fix a crashing application or any other fault. They are also used to provide a view of the program's structure when reverse engineering.
Article summary
Debugging information is information that describes a correspondence of elements in the source code, such as the names of variables and routines, to entities in the object code, which is found in an object file, such as a shared library or an executable. This kind of information allows a symbolic debugger to provide more a debugging experience that corresponds more closely to the source code. The debugging information may be compiled together with the module's binary file, or distributed in a separate file, or simply discarded during the compilation and/or linking. Because historically such information was associated with the symbol table (which originally was for the translation from exported identifier names to locations in the object file), they also commonly known as debug symbols. However, most debug information today exists outside of the symbol table, making this largely a misnomer. This information can be helpful while trying to investigate and fix a crashing application or any other fault. They are also used to provide a view of the program's structure when reverse engineering.
Key claims
No claims recorded.
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
No sources recorded.
Key claims and bibliography are generated from the same tracked claims and sources as the article page.