Rating: 
Summary: The Best Damn Book
Review: Just buy it. One of his advanced breakpoint tips alone will will save you more than enough time to pay for the book five times over.
Rating: 
Summary: lots of info let down by cd
Review: This book helped me learn a lot about Windows Development and debugging. I highly recommend to any serious developer.
Rating:
Summary: Ecellent
Review: This book helped me learn a lot about Windows Development and debugging. I highly recommend to any serious developer.
Rating:
Summary: Out of Print !(Huge Shame)
Review: This book is the final word on windows debugging. Not surprising since it comes from one of the authors of the award winning software: "Bounds Checker"I really enjoyed the chapter on x86 assembly. It covers what needs to be known to read through assembly code when the debugger tosses it at you. Trying to list all the good stuff in the book will take more time than I can devote right now. What I don't understand is why the book is now out of print. I'm sure some people out there still want to stick to native code and these people deserve to have this book. I'm happy I got mine before it went under.
Rating:
Summary: a long awaited book
Review: This excellent, easy to read book clearly explains how debuggers work, the win32 debug API, and includes source for a full featured win32 debugger. Mr Robbins has published many excellent debugging articles in his BugSlayer column, now he finally put it all together in a book.
Rating:
Summary: Dick
Review: This is a very good book which teaches one important lessons on window application debugging. Debugging is used to be a black art. Personally, I learnt in the hard way i.e. using the "pull you hair off" approach, :(. However, John Robbins focus on the issue on understanding the project scope, learning the sofware technology and using proper debugging tools. It makes the debugging a process which we, the developers, can learn. Althought, the book is focused on Windows application debugging but the principles and the rationale can be applied to other environment, e.g. Linux. Also the John Robbins writing style is fun and friendly. Highly recommended.
Rating:
Summary: Dick
Review: This is a very good book which teaches one important lessons on window application debugging. Debugging is used to be a black art. Personally, I learnt in the hard way i.e. using the "pull you hair off" approach, :(. However, John Robbins focus on the issue on understanding the project scope, learning the sofware technology and using proper debugging tools. It makes the debugging a process which we, the developers, can learn. Althought, the book is focused on Windows application debugging but the principles and the rationale can be applied to other environment, e.g. Linux. Also the John Robbins writing style is fun and friendly. Highly recommended.
Rating:
Summary: lots of info let down by cd
Review: This is the kind of book you wish you'd already read. The author includes quite a few real-life tips and insight. My main problem with the book is because its "advertised" #1 reason for buying it is just a tease. The author makes the point over and over about the amount of source code provided with the book on CD. The point here being if you want to actually use the tools he presents then you need to be able to build with the code provided . However, even though John Robbins points out that you'll need the dbghelp.h and dbghelp.lib files - THE .LIB FILE ISNT ON THE CD!!! This makes all the effort worthless. This isnt just any file - it is 1 of the only 2 really important files out of the whole CD. Granted Robbins claims these files are available as a free download from the Microsoft site - but what he fails to mention is that to get them you have to make a hefty SDK download to get them. Try as I might on several pc's on 3 different Windows platforms not once would the SDK install. Ok, maybe that's a problem with Microsft quality control, but Robbins shouldnt be requiring us to download this SDK just for 2 files that should be on the CD in his book. Maybe a 1 star rating is harsh, but I feel that justified given Robbins places this as the most important reason for buying his book. The result is that after reading only a part of the book you'll likely lose interest when you cant do anything useful. Sorry John -- but you need to debug your own CD ;-)
Rating:
Summary: Wow, John Robbins has done it again !
Review: Unbelievable, energetic John Robbins has slain yet another bug-beast with this "must have" developer's guide to preventing, finding, killing and eradicating bugs from your code ! This book is great and will revolutionize the ever-befuddling world of debugging. I highly recommend it to all software developers throughout the world.
Rating:
Summary: Five stars, but only for the right reader
Review: Use this book as an extensive tutorial/reference to the Visual C 6 IDE debugger. As such it is great: there's a wealth of information about VC's debugging facilities, debugging methods possible with this environment, Com-specific debuggin tricks, and general miscellanea. Most of people would never assimilate all this info without this book--not because it's not in the on-line docs, but rather because it's here and there, one bit every 200 pages--you'll simply never put it all together topically. The author did it for you. On the other hand, the book has no structure whatsoever (consider it a set of app notes/white papers in a single binding) and is Windows-specific in the highest degree. Its value as a general, platrofm- and tool-independent debugging reference is, while perhaps not zero, but rather insignificant. The writing is "magazinish", at times condesending, and somewhat infested with MS "humour", which I personally find annoying. So, if you work with Windows (NT) A WHOLE LOT, use Visual C++ v6, and write something more involved than mostly-GUI code, you will find this book a very valuable resource, worth the price and the five starts that I gave it. Yet if you are more of a "half-and-half" <g> (Unix/something else/Windows guy) perhaps it won't be as indispensable.
| 
