sapiensovni

Ebook Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers

This is why we recommend you to always see this resource when you require such book Debugging Windows Programs: Strategies, Tools, And Techniques For Visual C++ Programmers, every book. By online, you may not go to get the book shop in your city. By this on the internet collection, you can find guide that you actually intend to check out after for long time. This Debugging Windows Programs: Strategies, Tools, And Techniques For Visual C++ Programmers, as one of the suggested readings, tends to remain in soft data, as every one of book collections right here. So, you could likewise not await couple of days later to get as well as review the book Debugging Windows Programs: Strategies, Tools, And Techniques For Visual C++ Programmers.

Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers

Ebook Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers

This is your absolutely time ahead over as well as have particular routine. Reading as one the hobby to do can be done as practice. Even you may not be able to read on a daily basis, you option to select reading a publication to go along with in spare time is right enough. There are not all people have in this manner. Several likewise believe that reading will certainly be so monotonous.

Why should be this book? This is just how guide will certainly be referred. It is truly used to get rid of the understanding and motivations from guide. During this time around, it remains in the list of excellent books that you will certainly find in this globe. Not just individuals from that country, numerous international individuals likewise see and also obtain the representative info and also motivations. Debugging Windows Programs: Strategies, Tools, And Techniques For Visual C++ Programmers is just what we have to search for after obtaining the forms of guide to need.

It is likewise exactly what you will certainly get from getting this book as recommendation to enrich your quality and also understanding. It will show you just how kind a publication is. Every sentence and every web page of this Debugging Windows Programs: Strategies, Tools, And Techniques For Visual C++ Programmers will reveal you brand-new point. It will certainly not force you to know or keep in mind all sentences. The most points to constantly remember is the lesson or message that is informed in this book.

Be the first to download this book Debugging Windows Programs: Strategies, Tools, And Techniques For Visual C++ Programmers and allow reviewed by surface. It is quite easy to review this e-book Debugging Windows Programs: Strategies, Tools, And Techniques For Visual C++ Programmers since you don't have to bring this published Debugging Windows Programs: Strategies, Tools, And Techniques For Visual C++ Programmers almost everywhere. Your soft data publication could be in our kitchen appliance or computer so you can take pleasure in checking out anywhere as well as whenever if required. This is why lots varieties of people additionally check out guides Debugging Windows Programs: Strategies, Tools, And Techniques For Visual C++ Programmers in soft fie by downloading guide. So, be among them which take all advantages of reviewing the book Debugging Windows Programs: Strategies, Tools, And Techniques For Visual C++ Programmers by on-line or on your soft documents system.

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

Read more

From the Inside Flap

Debugging Windows programs is a large, complex subject. A book that covered all possible aspects of Windows debugging could easily be twice the size of this book. The problem with such a comprehensive approach to the subject is that the results would be so large and intimidating that few people would want to read it. Consequently, we had to draw the line somewhere and focus on some aspects of Windows debugging at the exclusion of others. Let's start by explaining how we chose to draw that line.The fundamental motivation behind this book is the belief that programmers' debugging skills could be much improved if they had access to better debugging information. Although plenty of debugging information is available, it is not currently in a form that a programmer can read and then have mastery of the subject. Too often the information is vague and incomplete, or the focus is on debugging tools instead of debugging concepts. The ultimate debugging tool is the programmer's mind, and too often that tool has been neglected. Mastering fundamental Windows debugging concepts will help you prevent many bugs and find the remaining bugs more efficiently, even if you are the most gung ho tool user.This book identifies the fundamental debugging skills required for effective Windows debugging. Once you have read a chapter, you should have that chapter's subject wired. Part I of the book focuses on debugging strategies to help you understand the debugging process and how to use the C++ language, assertions, trace statements, and exceptions to prevent, reveal, diagnose, and remove bugs. Part II focuses on debugging tools included in Visual C++ as well as Windows. Part III focuses on debugging techniques to help you get the most out of Visual C++ debugging tools, with special attention to debugging memory-related problems, multithreaded programs, and COM.Some subjects addressed here straddle the border between programming skills and debugging skills. However, since bug prevention is very much a part of debugging, you need to know the common programming mistakes in order to avoid making them. Most programming texts avoid the subjects of debugging and bug prevention, so these subjects need to be addressed.What's missing in the presentation is also notable. We have largely avoided discussing third-party debugging tools or any Microsoft debugging tools that are not part of Visual C++ (such as WinDbg) or Windows. There are several motivations for this decision. The obvious motivation is to stay focused on debugging concepts and not get side tracked by documenting tools. Another strong motivation is that Visual C++ programmers need better information on how to use the tools they already have. Finally, we doubt that we could say anything about these other tools that would be more helpful than the information provided by the tool vendors themselves. But I Use BoundsChecker . . . Some readers are now thinking, "But I use BoundsChecker, so why should I read this book?" Excellent question. Debugging tools, such as Compuware NuMega's BoundsChecker and Rationale Software's Purify, do an excellent job of finding many types of runtime errors--bad pointers and handles, memory corruption and leaks, bad Windows API parameters, and so on. What they don't do is help you understand the debugging process, including how to use the C++ language, assertions, trace statements, and exceptions to prevent and remove bugs, how to take full advantage of the debugging tools that are part of Visual C++ Windows, or how to debug multithreaded programs and COM--all of which this book does.Furthermore, these tools certainly do not detect all bugs, and they do nothing to help you prevent bugs. If you are totally dependent on debugging tools, you will be helpless when presented with bugs these tools don't find. In addition, using these tools requires you to perform an extra development step, and they can have a significant impact on runtime performance, whereas many of the bug-detection techniques described in this book happen automatically whenever you run the debug build and have a minimal impact on performance. Debugging is a complex puzzle, but these debugging tools will help you with only one piece. How to Read This Book Although our hope is that you will read this book from cover to cover, we realize that many readers are in a hurry and won't have the time to read a whole book in order to track down a bug. Consequently, each chapter is largely self-contained so you should be able to read only the chapters you need in the order you want. This self-containment approach means there are some bits of redundant material that apply to more than one chapter, although we tried to keep such redundancy to a minimum. We hope you will agree that this approach makes the book a much more useful reference.After the Contents, there is a list of answers to frequently asked questions, which can quickly guide you to solutions to many common debugging problems. Chapter 8 is also organized in this way, and either the FAQ list or the chapter can help you quickly find an answer to a specific debugging question.There are many different types of Windows programs, so there are many different types of debugging techniques. Debugging is presented from the point of view of the Windows API, as well as the MFC and ATL application frameworks. We have clearly identified the material that is specific to MFC and ATL; so if you're not using these frameworks, feel free to skip over those sections if you are in a hurry. If you're not in a hurry, you might want to read them because it is often useful to look at debugging from other points of view.Finally, each chapter contains key points of advice about debugging, which are presented in a special format as shown here.These tips highlight the most useful debugging ideas, make the text easier to scan, and will help you locate important debugging topics quickly. Windows Versions and Hardware To simplify the presentation, we refer primarily to the current versions of Windows, which at the time of this writing are Windows 2000 and Windows 98. Almost everything said here about Windows 2000 applies to Windows NT 4.0, and nearly everything said about Windows 98 also applies to Windows 95. We mention Windows NT 4.0 and Windows 95 only when referring to those specific versions of Windows.To further simplify the presentation, we assume you are using Windows on an Intel x86 central processing unit (CPU). Although most of this book is CPU independent, the specific CPU becomes a factor when you are reading hex dumps or debugging at the assembly-language level. For those of you doing assembly-level debugging on a non-Intel platform, you have our sympathy, but not much else. Who Is "I"? Although there are two names on the cover, we wrote this book using the first person. Each chapter tells its story from the point of view of a single author. Mike Woodring wrote Chapter 10, Debugging Multithreaded Programs, and Chapter 11, COM Debugging, whereas Everett McKay wrote the remainder. Consequently, the "I" in Chapters 10 and 11 refers to Mike Woodring, whereas the "I" in the other chapters refers to Everett McKay. For Updated Information The information in this book is based on Microsoft Visual C++ version 6.0. If you are using a later version of Visual C++, chances are the majority of this book is still accurate but a few details related to the compiler or debugger have changed. To help keep this book's information fresh, we will post any updates or corrections at windebug, along with selected debugging tools. Should you find any errors or out-of-date information, please let us know by sending an e-mail message to corrections@windebug.020170238XP04062001

Read more

See all Editorial Reviews

Product details

Paperback: 592 pages

Publisher: Addison-Wesley Professional; 1 edition (August 28, 2000)

Language: English

ISBN-10: 020170238X

ISBN-13: 978-0201702385

Product Dimensions:

7.3 x 1.4 x 9 inches

Shipping Weight: 2.1 pounds (View shipping rates and policies)

Average Customer Review:

3.9 out of 5 stars

13 customer reviews

Amazon Best Sellers Rank:

#932,572 in Books (See Top 100 in Books)

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

This book should have been included with the MS Visual C++ documentation. If you can say "My code doesn't have bugs, only features," then you may skip this book. I found this book full of tips and tricks and secrets of visual c++ debugging. Just by having this book on your side, you will save hours and hours of frustration trying to find that one line that's keeping you from going home. Beginning few chapters are basic debugging knowledge every visual C++ programmers should be aware of. It explains more of 'preventive' programming styles so that you notice your bugs before your customers. Various topics including assert and compiler options are well explained, much better than the ones you would find in the vc++ documentation. I was happy to finally see some explanation on Dr. Watson messages. In Chapter 6: Debugging with Windows, Woodring and McKay explains all the precious information buried in those memory dumps that we often ignore. After all, all those hexadecimal numbers got to mean something, right? If you have been always unsure about your multithread knowledge, this book contains a good section on multithread programming issues and how to monitor your threads from the debugger.And for those who can't sleep at night because of some odd bug buried in thousands of lines of code, I recommend jumping right into Chapter 12: Desperate Measures. You are probably too frustrated to think straight now. Let this book help you calm down and look through your code step by step. This chapter simply provides a code checking checklist that you should probably copy down and tape it to your monitor. For those of you that are starting a fresh batch of code and thinking about buying this book, my recommendation is to read this book first, then code. You'll be a lot happier later. And for those of you that have already written a few million lines of code and trying to debug, you can apply some of the techniques found in this book to build up confidence in your code. I suppose if you live dangerously ("Just let 'er rip and hope for the best"), then most of the things explained in this book will only seem annoying to you, but I'm sure most of you programmers out there would like to know a few neat debugging tricks to show off in front of your co-workers.

C++ bugs can be very difficult to find and can bring tears to the eyes of a programmer easily.(You know the bug is there but you just cant find it to save your life!)After reading the first few chapters of this book, I knew it was a winner.This book shows ways to find bugs in different kinds of C++ programs MFC,COM etc.The most important however is the chapter on memory bugs(a real pain)If you need to hunt down bugs, get this book and your monitor is less likely to end up smashed from your frustrations.This book also points the reader to a lot of other books which should make a better programmer of anyone who bothers to buy them.

If you write sofware for Windows using VC++, you cannot afford to not have this book. End of story. Everything that I'd scoured MSDN, MSJ, and news groups for the last 5 years to figure out about how Windows works from a user mode program mechanics point of view (PE format, DLL rebasing, symbols, etc) and debugging techniques is in this book (plus more stuff that I'd not yet found out about). It is well written and understandable. It works as a good overview of the topics and as a reference for dealing with a partiular problem, like post-mortem debugging, debugging memory or multi-threading problems, etc. Pick one up, you won't regret it.

The vast majority of recommendations are so simple, yet so effective. Even if you only read random sections of this book, it will be of immediate benefit. This book in conjunction with John Robbin's book (Debugging Applications) are invaluable in not just giving you tips on how to find bugs but much more importantly how to code defensively to reduce the chances of bugs occurring in the first place.As the authors mention in the preface, they are not many original ideas in the book - but it is a good consolation of publicly available information. The book adds value by explaining when to use certain techniques and when to use others e.g. Chapter 5 -Using exceptions vs. return values.Because the book is specifically geared to C++ programmers there are some fantastic macros. For instance _CoCreateServer which wraps CoCreateInstance but gives detailed error information if anything goes wrong. Chapter 9 - Debugging Memory was particularly useful. Being able to detect leaking memory in ATL components (just like MFC does) was worth the price of the book alone.My only criticism is the use of the Arial font which makes the book a little getting used to seeing on the printed page.

Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers PDF
Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers EPub
Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers Doc
Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers iBooks
Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers rtf
Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers Mobipocket
Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers Kindle

Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers PDF

Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers PDF

Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers PDF

Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers PDF