Don't buy this book; save a tree!

It says nothing about actually useful practices, like unit-testing. No thrilling bug hunting stories, just a collection of boring examples, written in "for dummies" style that made me want to close the book immediately.

While this book does something that I am in strongly in favor of, I don't agree with the approach. Barr presents a series of code segments that contain bugs and the reader is challenged to find the error(s). The bugs introduced into the code are fairly common, so finding them will be excellent practice for coders at all levels of experience. The segments of code are short, generally less than two pages, so finding the bugs does not require a great deal of searching.
The problem is that the programs are written in C, Python, Java, Perl and x86 assembly. If you are experienced in a particular language, then the bugs will probably not challenge you. However, if you are a novice in a language, the ten pages devoted to introducing the language will not be enough to get you up to speed. I have taught all of these languages and I found it difficult to shift from one language to another. The syntax differences between the languages are enough to confuse even people experienced in all of them. I am also unconvinced that finding bugs in a language you are not using and are unfamiliar with will make you a better programmer.
The general sequence of the bug presentations is:

*) A textual explanation of the problem.
*) The source code.
*) Suggestions of questions to consider.
*) Hints of operations to perform when stepping through the code.
*) Explanation of the bug(s).

Which is certainly a sound approach.
I dithered a bit when trying to settle on a ranking for this book, largely due to the multiple languages. In the end, I settled on three stars because I believe that if you go through this book, it is more likely that instead of doing a few things well, you will do many things poorly.

This book has a set of bugs to work through in C, Java, Perl, Python, and Assembler. The bugs range from rudimentary syntax mistakes to more complex and subtle bugs. Hints are given to help you along the way. These will definitely give you brain a spin. Much link the C lint bugs in that have been printed in Dr. Dobbs for years. If you enjoy logic puzzles and bug hunting you will like this book.

Adam Barr steps you through code analysis in a logical fashion, guiding you around some obvious and not so obvious pitfalls. His writing style makes it easy to understand his concepts. Adam's selection of languages benefits programmers of all backgrounds. I especially enjoyed looking through the Python examples. The language summary at the beginning of each chapter is a great idea to acquaint newcomers to a language. Experienced programmers as well as hobbyists will find great value in the examples. Not only will you become a better debugger, you will become a better programmer.

If you're a programmer who has to look at code that others have written, you'll appreciate this book... Find The Bug by Adam Barr (Addison-Wesley).
Chapter list: Bug Classification; Tips on Walking Through Code; C; Python; Java; Perl; x86 Assembly Language; Classification of Bugs; Index of Bugs by Type; References; Index

This is a excellent text to help you improve your skills on reading code and mentally debugging it. There are 10 short program or routines for each of the five languages. Your goal is to walk through the code and figure out what is the hidden error in it. There are three or four suggestions if you need help thinking it through, a couple of direct hints to focus your thoughts, and a complete explanation at the end. Even though you may not be familiar with some of the languages, Barr gives you a basic coverage of the fundamentals at the beginning of the chapter so that you can see if you are able to spot the error. Add to all that some good information on how best to walk through code, and you end up with a book that should be part of every developer's training. If you're part of a development group that does code walkthroughs, this would be an excellent guide to help everyone become more effective during the process.

A good way to step outside your normal thought processes and improve your skills... good stuff.