Books : Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers (DevelopMentor Series)

In association with Amazon.com
 View Shopping Cart or Checkout 

Author name: Everett N. McKay, Mike Woodring

 : Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers (DevelopMentor Series)
View Bigger Picture

Regular marked price: $44.95
Discount Price: $38.01
Cost Savings: $6.94 (15%)
Price fluctuation possible.

Used Price: $13.70
Third Party New Price: $19.99


How soon does it ship: Normal ship time within one day



Shipping? Absolutely FREE if you qualify for Super Saver Shipping.
Type of bind: Paperback
Dewey Decimal Number: 005.14
EAN num: 9780201702385
ISBN number: 020170238X
Label: Addison-Wesley Professional
Manufacturer: Addison-Wesley Professional
Quantity: 1
Page Count: 592
Printing Date: August 28, 2000
Publishing house: Addison-Wesley Professional
Sale Popularity Level: 454271
Studio: Addison-Wesley Professional




Other books you might be interested in perusing:

Editor's Notes and Comments:

Product Description:
(Pearson Education) Shows readers how to prevent bugs by taking advantage of the Visual C++ development tools and writing code in a way that makes certain types of bugs impossible. Provides specific solutions to the most common debugging problems. Softcover. DLC: Debugging in computer science.

Amazon.com Review:
Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers sounds like it might focus on using a debugger exclusively, but this book is actually a wide-ranging tour of how to write better, more robust Visual C++ code that can be debugged more easily. Mixing plenty of nuts-and-bolts tips with higher-level strategies for effective testing, Debugging Windows Programs offers plenty of valuable expertise for any working C++ programmer.

The focus is on providing practical tips for more successful debugging, but many of the suggestions are for tweaking the way in which you write C++ code. Early sections examine how to take full advantage of assert statements (whether in C, MFC, or custom functions), which can be used to write safer code; trace statements, which are used to log debug messages, are covered, too. (Chances are that you haven't seen all of the APIs; luckily, they're rounded up for you here.) There are also numerous tips about C++ style, like how to choose readable variable names, along with the debugging dos and don'ts of working with errors, exceptions, COM objects, and threads.

Chances are, even if you are an experienced Visual C++ programmer, you'll learn something useful about how to get more out of the C++ debugger from the last sections of this book. From the right compiler and linker switches (which can be mysterious) to how to customize watch variables by tweaking the configuration files in C++, you'll learn how to be more productive with this tool. The text concludes with another useful section, an FAQ-style listing of dozens of common debugging questions and answers.

Although it's highly practical, the book also recommends thinking about your code, applying strategies for each aspect of debugging features consistently and effectively. The bottom line is that you not only will find bugs in present code, but also you'll design code that's easier to test and debug in the future. In all, Debugging Windows Programs delivers a good mix of practical tips and strategies that'll help C++ programmers create more robust (and testable) code. --Richard Dragan

Topics covered:
  • The debugging and testing process
  • Tips for writing better Visual C++ code
  • Assertions (C, MFC, and custom assert statements)
  • Logging output with trace statements (including trace APIs)
  • Exception handling and debugging
  • First-chance and last-chance exceptions
  • Tips for better debugging in C++
  • Naming conventions
  • Postmortem
  • Just-in-time (JIT) and remote debugging

  • Using map and .pdb files
  • Compiler and linking options
  • Debug windows
  • Customizing the C++ debugging environment
  • Basic and advanced debugging techniques
  • Catching memory leaks with the debug heap
  • Debugging multithreaded programs (including avoiding race conditions and deadlock)
  • A primer for COM debugging
  • Frequently asked questions and answers about debugging




  • Customer Reviews
    User popularity level:  out of 5 stars

    Rated by buyers 3 out of 5 stars - Useful but expensive and poorly produced
    Lots of useful information, particularly the tips for debugging release executables, but very poorly produced as a book.

    The copy I received (and returned) appeared to have been made from a badly cropped set of bound photocopies. This is completely unacceptable at this price.



    Rated by buyers 4 out of 5 stars - Very good but a little dated
    This is a very good book, although it is now a little dated. The explanations on customizing watch windows, and tuning default step over behavior has already payed for itself in terms of time savings.



    Rated by buyers 2 out of 5 stars - Bad Print
    I bought this book and was so shocked to see the print quality of the book. All the left inside pages had incomplete sentences due to print. Not only this the words break into subsequent sentences. I have never seen such a bad quality of print in my life. The font is pathetic. I have to say this but I can guarantee the technical writers/review did not review this book after the print because its impossible to read the pages beacuse the sentences are incomplete and words left out b'cos of mis print.
    Is this only my copy or every copy has this problem. Can somebody confirm this? I am surprised how anybody has not noticed this?



    Rated by buyers 5 out of 5 stars - A MUST HAVE. PERIOD!
    This is the best book in debugging I have ever seen. What I like most about this book in addition to the technical value it has, is being concise and more to the point. There no much unnecessary detail. For people with little patience on reading like me, this will take you directly to the problem you have.

    - The book covers the most common issues a developer needs while debugging his application. I will not go into detail, but things like debugging memory problems or finding where your application crashed (in the source code level) having the crash address, to deadlocks and multithreading.

    - The best chapter in the book in my openion is the multithreading and deadlock analysis. The best treatment in a book. Its coverage is even better than John Robin's book.

    If you have to buy only one book about debugging, buy this one. Only if you are rich, and willing to buy another one just for the sake of it, buy John Robin's



    Rated by buyers 5 out of 5 stars - Pays for itself within your very first project
    I wish I had this book before - only discovered it recently. This book pays for itself within your very first project. Surgical precision-like debugging. Wealth of information. I hope they are working on a sequel to this book for .Net development.

    see more


    Find other books like this one:

     


    Psoriasis Fish / Breathing And Anxiety Attacks / Taken Alive / Backlog Studies / Enid Blyton /
    Vancouver Business Gift Baloo Book Jungle Romantic Gift Idea Alice In Wonderland Clip Art Young Sherlock Holmes Autism Shirt Sherlock Holmes The Mystery Of The Mummy Christmas Wedding Invitation Islamic Education Unusual Birthday Gifts History Of The Wizard Of Oz

    Home - Soccer - Swords - Tennis - Baseball
    Basketball
    Body Building
    Hockey
    Football