- Paperback: 280 pages
- Publisher: No Starch Press; 1 edition (18 September 2008)
- Language: English
- ISBN-10: 9781593271749
- ISBN-13: 978-1593271749
- ASIN: 1593271743
- Product Dimensions: 17.8 x 2.3 x 23.5 cm
- Average Customer Review: 1 customer review
Amazon Bestsellers Rank:
#3,73,762 in Books (See Top 100 in Books)
- #206 in Books > Computing, Internet & Digital Media > Programming & Software Development > Languages > C & C++ > C
- #1280 in Books > Textbooks & Study Guides > Higher Education Textbooks > Computer Science > Software Design & Engineering
- #1297 in Books > Computing, Internet & Digital Media > Programming & Software Development > Software Design, Testing & Engineering > Software Architecture
The Art of Debugging with GDB, DDD, and Eclipse Paperback – Import, 18 Sep 2008
Customers who bought this item also bought
Customers who viewed this item also viewed
About the Author
Norman Matloff, a computer science professor at UC Davis, is the author of several popular public-domain software packages and online tutorials.
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter mobile phone number.
Showing 1-1 of 1 reviews
There was a problem filtering reviews right now. Please try again later.
Most helpful customer reviews on Amazon.com
My experience with command-line debugging has been trail and error which is useful when information is lacking. When you have a more complete body of information about a tool or process, then you can optimize your efforts and achieve better results. Such is the case with this book and how it will equip persons with the concepts of command-line debugging that they can use in any environment where such debuggers may be available.
If you write lots of code in a language that allows you to use gdb, you probably can save time learning how to use gdb or one of its front-ends. Learning how to use a debugger is not only about learning its options and commands, but how you should use it, and this observation shaped this well-written book.
Currently, I think that one should learn programming with the aid of a debugger. Not only would inspecting exactly what happens at each line be didactic, it would help students immensely later on.
I'd like to see a reviewed version of this book including reverse debugging; feature added after the publication of this book.