Authors:
- Not restricted to a specific combination of compiler, debugger, and operating system
- At the same time it is not too high level
- Contains examples that can be reproduced with open source software on different UNIX and Windows platforms
- Remains focused on software debugging and does not drift into areas such as fixing broken hardware
- Covers the full range of real-word debugging tasks including memory problems, linker problems, profiling, parallel programs and static checkers in addition to covering basic and advanced source code debugging topics
- Written by professionals presenting effective solutions to real-world problems
- The authors of the book have felt the pain both while debugging tough problems and teaching others how to crack the (broken) code
- Covers the most important real-world problems, and presents effective solutions that can be applied immediately
This is a preview of subscription content, log in via an institution to check for access.
Table of contents (13 chapters)
-
Front Matter
-
Back Matter
About this book
The Developer’s Guide to Debugging is a book for both professional software developers seeking to broaden their skills and students that want to learn the tricks of the trade from the ground up. With small examples and exercises it is well suited to accompany a CS course or lecture. At the same time it can be used as a reference guide to address problems as the need arises. This book goes beyond the level of simple source code debugging scenarios. In addition, it covers the most frequent real-world problems from the areas of program linking, memory access, parallel processing and performance analysis. The picture is completed by chapters covering static checkers and techniques to write code that leans well towards debugging. While the focus lies on C and C++, the workhorses of the software industry, one can apply many techniques described in The Developer’s Guide to Debugging to programs written in other languages.
Reviews
From the reviews:
Thorsten Grötker, Ulrich Holtmann, Holger Keding, and Markus Wloka speak directly to the entrenched developer, give straight-forward advice on solving debugging problems and come up with solutions real fast. Whether it is solving memory problems, debugging parallel programs, or dealing with problems induced by your very tool chain - this book offers ?rst aid that is tried and proven.
When dealing with today’s programs, especially those written in C and C++, we’ll still spend some time on debugging – and that’s where The Developer’s Guide to Debugging provides truly priceless advice.
Saarland University, Spring 2008 - Andreas Zeller
"Grötker and colleagues tell readers how to set up a structured process for debugging, categorize the possible bugs, demonstrate writing programs so that they may be more easily debugged, and examine the various tools available. … Surely an essential resource for professional programmers. Summing Up: Highly recommended. Academic, professional, and two-year technical program libraries, all levels." (R. P. Sarna, Choice, Vol. 46 (6), February, 2009)
"This is a comprehensive guide to debugging C and C++ programs. … This is the only book I have seen that not only exhaustively covers C/C++ debugging in most common environments, but also gives one a choice of tools to use for each type of problem. I recommend the book to C developers, or as a reference for instructors of C programming courses." (P. Spoerri, ACM Computing Reviews, January, 2009)
Authors and Affiliations
-
Synopsys Inc, Aachen, Germany
Thorsten Grötker, Ulrich Holtmann, Holger Keding, Markus Wloka
Bibliographic Information
Book Title: The Developer's Guide to Debugging
Authors: Thorsten Grötker, Ulrich Holtmann, Holger Keding, Markus Wloka
DOI: https://doi.org/10.1007/978-1-4020-5540-9
Publisher: Springer Dordrecht
eBook Packages: Computer Science, Computer Science (R0)
Copyright Information: Springer Science+Business Media B.V. 2008
Edition Number: 1
Number of Pages: XX, 224
Topics: Software Engineering/Programming and Operating Systems, Programming Languages, Compilers, Interpreters, Circuits and Systems