R. Stallman and R. Pesch. Using GDB: A Guide to the GNU Source-Level Debugger. July 1991.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....as inserting print statements, commenting out sections of scripts, or having a deep intuition of the underlying implementation. Obviously, none of these techniques are particularly elegant. An alternative approach is to run the application under the control of a traditional debugger such as gdb [17]. Although this provides some information about the error, the debugger mostly provides detailed information about the internal implementation of the scripting language interpreter instead of the script level code that was running at the time of the error. Needless to say, this information isn t ....

....In this case, a heuristic approach that examines the machine code for each function on the call stack can be used to determine where the registers might have been saved. This approach is used by gdb and other debuggers when they allow users to inspect register values within arbitrary stack frames [17]. Even though this sounds complicated to implement, the algorithm is greatly simplified by the fact that compilers typically generate code to store the callee save registers immediately upon the entry to each function. In addition, this code is highly regular and easy to examine. For instance, on ....

R. Stallman and R. Pesch, Using GDB: A Guide to the GNU Source-Level Debugger. Free Software Foundation and Cygnus Support, Cambridge, MA, 1991.

....hand written to perform the necessary tag update operations to capture their type behavior. Finally, our tool lends itself naturally to interactive debugging. When a warning or error message is issued, a signal (SIGUSR1) is sent, and can be intercepted by an interactive debugger like GDB[6]. The user is then able to examine memory locations, including the mirror, and make use of GDB s features to better track down the cause of an error. 4 Experiments To test the e#ectiveness of our debugging tool, we used Fuzz[7] to find Solaris utilities that crash on some inputs, and ....

R. Stallman and R. Pesch. Using GDB: A Guide to the GNU Source-Level Debugger. July 1991.

....of the tools is not possible. Combining a traditional debugger with our Observation Engine is a good way to track tool internal bugs (algorithm prob lems, memory allocation errors, etc. So, we plan to integrate our observation tool into a public domain traditional debugger such as the GNU gdb [14]. Our work has been very useful to find bugs and synchronization problems while developing tools for our integration framework. The Observation Engine is intensively used to develop the new version of the modeling framework AMI [4] based on TOPIC SE. ....

Stallman Richard M. and Pesch Roland H. , "Using GDB: A Guide to the GNU Source-Level Debugger ", July 1991.

....in this project s static analysis phase. As discussed above, instrumented code currently issues a warning message when a value of one type is assigned to a location of a di#erent type. It may be useful to add an option so that in such cases control is passed to an interactive debugger like GDB[8] (e.g. by sending a signal that is caught by GDB) This would permit the programmer to use the interactive functionalities of GDB to examine the program state to understand the cause of the type inconsistency warning, and whether it indicates a logical error. The programmer may also want the ....

R. Stallman, R. Pesch. Using GDB: A Guide to the GNU Source-Level Debugger. July 1991.

....type behavior. However, we have not yet written wrappers for variableargument functions (like scanf) Finally, our tool lends itself naturally to interactive debugging. When a warning or error message is issued, a signal (SIGUSR1) is sent, and can be intercepted by an interactive debugger like GDB[20]. The user is then able to examine memory locations, including the mirror, and make use of GDB s features to better track down the cause of an error. 3.4 Instrumentation Example To illustrate the syntax directed transformations that are performed to instrument C expressions, consider ....

R. Stallman and R. Pesch. Using GDB: A Guide to the GNU Source-Level Debugger. July 1991.

....conditional breakpoints and automating program testing. Debuggers that support programming facilities do exist, but often the language is idiosyncratic to either the debugger or the source language, or both, and hard to learn. Most debuggers are large and complex programs; for example, gdb [14] is about 150,000 lines of C. This complexity has some unfortunate consequences. First, debuggers are often themselves buggy, because, like any large program, their complexity and size makes them prone to errors and to inconsistent behaviors on different platforms. Second, debuggers are usually ....

R. M. Stallman and R. H. Pesch. Using GDB: A guide to the GNU source-level debugger, GDB version 4.0. Technical report, Free Software Foundation, Cambridge, MA, July 1991.

....research and development communities on several levels of abstraction, including compilers, computer architecture, and databases. By far the most comprehensive treatment of debugging has been conducted in the software compiler domain. Several debuggers, such as VAX DEBUG [Bea83] Dbx [Lin90] GDB [Sta91], and more recently Purify [Has92] has been widely used. Majority of efforts related to debugging in the compiler domain has been dedicated to symbolic level debugging on uniprocessor computers. It has been noticed that debugging often significantly slows done execution of the program. For ....

R.M. Stallman, R.H. Pesch, "Using GDB: A guide to the GNU source-level debugger, GDB version 4.0, Technical Report, Free Software Foundation, Cambridge, MA, 1991.

....intermediate representations and code generator generators. We are developing techniques for building retargetable, multiple target debuggers. This paper describes the design and implementation of ldb, a prototype retargetable debugger. ldb is a source level debugger like gdb or dbx [15, 22]. It can be used with C programs compiled with lcc [11] a retargetable compiler that generates code for the MIPS R3000, Motorola 68020, SPARC, and VAX architectures. Users can set and remove breakpoints, start and stop programs, evaluate expressions, and make assignments to variables. ldb s ....

....reduce this kind of re implementation effort. ldb has a fixed name resolution algorithm, but its implementation of printing values and its interaction with the expression server are independent of C. The name resolution algorithm could handle nested procedures, but not overloading. gdb 4. 0 [22] supports 20 different target machines and many different versions of Unix, but of its more than 150,000 lines, over 47,000 are noted in the documentation as machine dependent. This figure does not include over 10,000 lines that deal with machine dependent object code formats like a.out and COFF. ....

R. M. Stallman and R. H. Pesch. Using GDB: A guide to the GNU source-level debugger, GDB version 4.0. Technical report, Free Software Foundation, Cambridge, MA, 1991.

....It usually involves rewriting most of the code that deals with symbol tables and with object code formats, because these vary widely with architectures and operating systems. Similarly, each architecture and operating system has its own facilities for accessing and controlling the target. gdb [18], a widely used debugger on many Unix platforms, illustrates the complexity involved even for a single operating system: gdb is more than 150,000 lines of C of which over 47,000 is machine dependent. This paper describes the design for a debugger that disentangles the machinedependent parts of a ....

....A particular implementation of the nub interface might serve more than one compilation system or more than one debugger. For example, a Unix nub implementation that understood Unix style executable files and symbol table formats could support traditional source level debuggers, like gdb [18] and dbx [10] and high level debuggers, like Duel [7] But different debugger design goals would often yield different nub implementations, even on the same architecture. The sections that follow describe cdb and its nub, which were designed to be as machine independent as possible. Example: cdb ....

R. M. Stallman and R. H. Pesch. Using GDB: A guide to the GNU sourcelevel debugger, GDB version 4.0. Technical report, Free Software Foundation, Cambridge, MA, July 1991.

....additional variables or control constructs. Other capabilities include concise ways of printing parts of large data structures. Duel is derived mostly from C, Icon [6] a very high level string processing language, and, to a lesser extent, from APL and LISP. Duel is implemented on top of gdb [13], a traditional source level debugger for C. Design Duel is an expression oriented language in which expressions can return a sequence of values. Operators permit these sequences to be manipulated in novel ways to achieve the goal of concise state exploration. As a simple example, x[0. 9] 1 ....

R. M. Stallman and R. H. Pesch. Using GDB: A guide to the GNU source-level debugger, GDB version 4.0. Technical report, Free Software Foundation, Cambridge, MA, 1991.

....monitoring, instruction simulators and dynamic linkers. A discussion of related work is presented here. Debugging primitives, which form the core of Dynascope primitives, are usually provided by the operating system [3, 22, 38] Debuggers rely on these primitives to carry out their operations [25, 30, 44]. Because operating systems provide different debugging primitives, debuggers must be carefully engineered to support porting to different platforms [37] Significant amount of research has been carried out recently to provide high level debugging abstractions and languages [12, 35, 36, 49] Some ....

R. M. Stallman and R. H. Pesch. Using GDB: A guide to the GNU source-level debugger, GDB version 4.0. Technical report, Free Software Foundation, Cambridge, MA, 1991.

....interface, we deliberately do not support an undo redo system for speculative computing or parallel worlds of execution. 2. 4 Debugger Interface The debugger uses a screen, keyboard, and mouse driven interface, implemented as an extension to the GNU Emacs editor, roughly in the style of gdb (Stallman and Pesch, 1991). It is independent of the debugger implementation and, to a large degree, of the specific functionality the debugger provides. Whenever execution halts under debugger control at a particular event, the corresponding source code is displayed with a pointer to the current site; the user can select ....

....but it is orders of magnitude faster than the partial evaluation approach, and produces more efficient, direct style instrumented code. 9. 2 Time Travel Our debugger s user features, which include value querying, breakpointing, and single stepping, are fairly ordinary (Beander, 1983; Linton, 1990; Stallman and Pesch, 1991); our system is unusual because it integrates these features with a flexible time travel mechanism. Although reverse execution is not provided by many commercial debuggers, it has a long research and prototyping history. Most previous systems have implemented reverse execution by building a log of ....

Stallman, R. M. and Pesch, R. H. (1991). Using GDB: A Guide to the GNU Source-Level Debugger (GDB version 4.0). Free Software Foundation, Inc.

No context found.

R. Stallman and R. Pesch. Using GDB: A Guide to the GNU Source-Level Debugger. July 1991.

No context found.

R. M. Stallman and R. H. Pesch. Using GDB: A guide to the GNU source-level debugger, GDB version 4.0. Technical report, Free Software Foundation, Cambridge, MA, 1991.

No context found.

R. M. Stallman and R. H. Pesch, "Using GDB: A guide to the GNU source-level debugger", GDB version 4.0. Technical report, Free Software Foundation, Cambridge, MA, 1991.

No context found.

R. Stallman and R. Pesch. Using GDB: A Guide to the GNU Source-Level Debugger. July 1991.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC