Rating:
Author: Jonathan B. Rosenberg
ISBN : B003VIWZCY
New from $35.63
Format: PDF
Download file now How Debuggers Work: Algorithms, Data Structures, and Architecture [Kindle Edition] Free Download from mediafire, rapishare, and mirror link A total guide to debuggers: what they do, how they work, and how to use them to produce better programs
"Debuggers are the magnifying glass, the microscope, the logic analyzer, the profiler, and the browser with which a program can be examined."-Jonathan B. Rosenberg
Debuggers are an indispensable tool in the development process. In fact, during the course of the average software project, more hours are spent debugging software than in compiling code. Yet, not many programmers really know how to constructively interpret the results they get back from debuggers. And even fewer know what makes these complex suites of algorithms and data structures tick. Now in this extremely accessible guide, Jonathan B. Rosenberg demystifies debuggers for programmers and shows them how to make better use of debuggers in their next projects.
Taking a hands-on, problem-solving approach to a complex subject, Rosenberg explains how debuggers work and why programmers use them. Most importantly, he provides practical discussions of debugger algorithms and procedures for their use, accompanied by many practical examples. The author also discusses a wide variety of systems applications, from Microsoft's Win32 debug API to a large parallel architecture.Download latest books on mediafire and other links compilation How Debuggers Work: Algorithms, Data Structures, and Architecture Free Download
- File Size: 5024 KB
- Print Length: 272 pages
- Publisher: Wiley; 1 edition (October 11, 1996)
- Sold by: Amazon Digital Services, Inc.
- Language: English
- ASIN: B003VIWZCY
- Text-to-Speech: Enabled
X-Ray:
- Lending: Enabled
- Amazon Best Sellers Rank: #978,767 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
How Debuggers Work: Algorithms, Data Structures, and Architecture Free Download
I recall the time, as I worked on a large parallel Unix debugger, and only slowly collected facts and scraps of necessary knowledge to progress. I always wondered, why not a single book was written, which would be solely devoted to the architecture, design and implementation of symbolic debuggers?
As I saw this book announced, my expectations were high. Could this be a help in organizing my knowledge about debuggers, collected so far from semi confidential industry reports or white papers, 3-4 dissertations, several implementations, plus some 10-15 conference papers with vague descriptions of implementations, claims of spectacular achievements or with mere theoretical ideas?
No, unfortunately this is not so. This book, or rather "a booklet" is very incomplete. It literally did not told me any single detail which I would not have known already. For example, missing is the description of the very standard Unix interface to control and hold a process. Since this is not a scientific book providing more generic foundations about process tracing (such as tracking of very long time running programs, replay techniques, generating snapshots etc. etc.) than I would at least expect a solid practice orientation. This should include a complete discussion of several assemblers and typical architectures, because they provide sometimes completely different means of implementing breakpoints, watchpoints or of support for threads. In many cases a debugger must be, or can be supported by a cooperating compiler. Several interesting ideas have been implemented in the back ends, which may greatly help supporting breakpoints, finding function prologues, dealing with exceptions and asynchronous signals.
Download Link 1