The Art of Debugging with GDB and DDD
Publisher: No Starch Press
Released: September 2008
Pages: 280
Description
Table of Contents
Product Details
About the Author
Recommended for You
Recently Viewed
Learning GNU Emacs, 3rd Edition
By Debra Cameron, James Elliott, Marc Loy, Eric S. Raymond, Bill Rosenblatt
December 2004
Ebook: $35.99
Print & Ebook: $49.49
Print: $44.99
RESTful .NET
By Jon Flanders
November 2008
Ebook: $31.99
Print & Ebook: $43.99
Print: $39.99
Apache: The Definitive Guide, 3rd Edition
By Ben Laurie, Peter Laurie
December 2002
Ebook: $35.99
Print & Ebook: $49.49
Print: $44.99
Customer Reviews

REVIEW SNAPSHOT®

by PowerReviews
oreilly The Art of Debugging with GDB and DDD
 
4.0

(based on 1 review)

Ratings Distribution

  • 5 Stars

     

    (0)

  • 4 Stars

     

    (1)

  • 3 Stars

     

    (0)

  • 2 Stars

     

    (0)

  • 1 Stars

     

    (0)

REVIEWS

Reviewed by 1 customer

Displaying review 1

Back to top

 
4.0

Informative for GDB Usage

By Roger

from North Pole, AK

Pros

  • Accurate
  • Concise
  • Easy to understand
  • Helpful examples
  • Well-written

Cons

  • Personal Opinions
  • Some Grammar

Best Uses

  • Expert
  • Intermediate
  • Novice
  • Student

Comments about oreilly The Art of Debugging with GDB and DDD:

A Very good read. Teaches users how to use all of the features of GDB.

But there's one thing the author(s) kept saying which troubled me. They severelly kept underrating the usage of printf for debugging with statements such as "it makes code ugly" or "you waste time coding in printf's".

This is not true at all. Matter of fact, I prefer code to be cluttered with printf's as they're usually used with a "-v" command line switch to print verbose debugging. A non-programmer and non-gdb user can use this debug method quite effectively except for segfaults. They then could use strace quite effectively.

As for time wasting coding printf's? Code them once and ifdef them or use them with a -v switch. Whereas GDB, each time you start a new GDB session, you need to retype everything if you haven't saved the settings within a .gdbinit file.

However, for code without any such inline printf's, gdb shines. But again, if the coder didn't use any printf's for debugging, it makes you wonder how good the code is?

But still, GDB looses no value at all, even if everybody uses printf's for debugging.

I've needed GDB many times to troubleshoot segfaults and other bugs.

About the only thing that bothered me in the book was how the author(s) taught more then two debuggers at once. I was able to keep track of GDB/DDD, but then they also taught the same functions for Eclipse's GDB interface which was a little confusing. The Eclipse interface should have had a chapter after explaining all of the GDB functions instead of intermingling. To work around this, a reader can simple skip the Eclipse related sections and then return to them at a later time.

This book also goes into a little detail of other debugging techniques such as strace/ltrace, along with some other information.

Again, a very good read if you code and debug! I give it 4 out of 5 stars.

Displaying review 1

Back to top

 
Buy 2 Get 1 Free Free Shipping Guarantee
Buying Options
Save a Tree - Go Digital  what is this?
Ebook: $31.95
Formats: ePub, Mobi, PDF
Print & Ebook: $43.95
Print: $39.95