Looking for:
Pluralsight advanced windows debugging download |
GitHub - fengjixuchui/AdvancedWindowsDebugging: Advanced Windows Debugging Book Code Samples.Pluralsight advanced windows debugging download
Reliable and realistic information about Windows debugging has always been scarce. To help you find real solutions fast , this book is organized around real-world debugging scenarios.
Hewardt and Pravat use detailed code examples to illuminate the complex debugging challenges professional developers actually face. Mario Hewardt is a senior design engineer with Microsoft, and has worked extensively in the Windows system level development area for the last nine years. He is currently involved with designing and implementing the next generation management protocol for Windows Longhorn.
Daniel Pravat is a senior design engineer with Microsoft and has worked in the Windows division, primarily within the Windows management area. He is currently leading a development team that has the responsibility of shipping the most reliable management platform for Windows Longhorn.
NET Debugging. With nearly two decades at Microsoft, he has worked with the development of Windows starting from Windows 98 up to Windows Vista.
Mario has also worked closely with enterprise customers as a Dedicated Developer Premier Field Engineer helping ensure that customers build their solutions on the Microsoft stack in the most efficient and reliable way possible. Mario lives in Washington state with his wife, daughter and two dogs.
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness. Frequently bought together. Total price:. To see our price, add these items to your cart. Some of these items ship sooner than the others.
Show details Hide details. Choose items to buy together. This item: Advanced Windows Debugging. Only 1 left in stock - order soon. Get it as soon as Saturday, Jun Inside Windows Debugging Developer Reference. Only 9 left in stock more on the way.
Windows Internals, Part 1: System architecture, processes, threads, memory management, and more Developer Reference. In Stock. Customers who viewed this item also viewed. Page 1 of 1 Start over Page 1 of 1. Previous page. Tarik Soulami.
Pavel Yosifovich. Windows Kernel Programming. Windows Internals, Part 2 Developer Reference. Andrea Allievi. Mario Hewardt. Randall Hyde. Next page. Start reading Advanced Windows Debugging on your Kindle in under a minute.
Don't have a Kindle? About the authors Follow authors to get new release updates, plus improved recommendations. Daniel Pravat. Brief content visible, double tap to read full content. Full content visible, double tap to read brief content. See more on the author's page. Customer reviews. How customer reviews and ratings work Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
Learn more how customers reviews work on Amazon. Top reviews Most recent Top reviews. Top reviews from the United States. There was a problem filtering reviews right now.
Please try again later. Verified Purchase. So I've had this book on my shelf almost 12 years as I bought it right before leaving a job that did windows dev and went to linux and never looked back. The pandemic had me digging deep into the stack of unread books and this finally got to the top of the list. While a lot of the book is focused on specific commands and OS primitives, I found this to be the only book I have ever read on how to use a debugger to find specific issues.
Its like taking a seat next to the smartest guy on your team while he walks through a problem. There are sample programs and scenarios you walk through while finding bugs.
My only gripes are that small scale samples make the surface area small- the problem comes when you have dozens of threads and a whole morass of code you only scratch the surface of. While I was able to follow the debug sessions, but putting them to use effectively is going to be more difficult. You will need a winxp vm to really play along with the examples. Overall though, this was the best book on debugging I have ever read. I wish something similar was around for gdb.
This is a book for advanced MS Windows developers. It goes deeply into the debugging process and it doesn't have an introduction for beginners or intermediate programmers. This is a vintage book and has testing processes for Vista. The writing is dry and to the point but effective.
I found the kernel dumps and the stack information to be time consuming and far too manual to be productive. I have found the people at Microsoft to be mired in this environment of command line investigation. They seem unable to creatively produce a tool to automate this process and produce a convenient process that is both effective and proper for programmers who aren't familiar with this intricate method of investigation.
However, it is good to know how much time and training the process requires to produce detailed results. If you are trapped in the intricacies of debugging IPC, service errors, or long running problems this book may hold the answers. Otherwise, the answer to what you are looking to accomplish will be found in the standard debugging tools and error notification processes.
This is the book I wanted to read when I started doing Windows crash dump analysis more than 5 years ago. So I had to learn from day-to-day experience and WinDbg help. Now WinDbg is a de facto standard in debugging and troubleshooting on Windows platforms and the book comes at the right time to teach the best practices and techniques. I'm reading it sequentially and I'm on the page at the moment and I have already learnt techniques and debugging strategies I missed due to certain habits in using WinDbg.
See my real time reading notes on Software Generalist blog. Even if you do mostly memory dump analysis and not live debugging of your product, you also will learn a lot to apply in your day-to-day problem identification and troubleshooting.
Absolutely must have for any Windows software engineers, escalation engineers and technical support engineers willing to advance their debugging skills. I have little to add to the effusive praise of previous reviewers. This is a one-of-kind book. An instant classic. Beware, however. If you're not comfortable with arcane command syntax, bits and bytes, and such this will be painful to incomprehensible for you.
On the other hand, I dare say you will never be a true Master Debugger until you have a good grasp of this material. You would do well to start with Debugging Microsoft.
NET 2. NET and Microsoft Windows. Both will give you an easier introduction to WinDbg. The latter, older volume has much more information on native code debugging than the newer version.
As they also cover the Visual Studio debugger in detail, most developers need go no further than one of these. NET debugging that isn't possible with Visual Studio alone. For that matter, the. John Robbins author of the previously mentioned books states in Chapter 6 of the latest version that "in our consulting work at Wintellect, which as you know works on the toughest bugs, we use WinDBG nearly 70 percent of the time.
Watch out for the font used in the listings though. Not being a master myself, I've been stumped for quite a while because the letter 'l' looks like the number '1' in the font they use.
I've been assiduously following the examples line-by-line. I also recall being stumped because of an error or two in the text, though I admit I can't find them now.
No comments:
Post a Comment