Relevant bibliographies by topics / Debugger

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Debugger'

Author: Grafiati
Published: 4 June 2021
Last updated: 26 April 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Debugger.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Debugger"

1

da, Cruz, Pedro Henriques, and Maria Pereira. "ALMA versus DDD." Computer Science and Information Systems 5, no. 2 (2008): 119–36. http://dx.doi.org/10.2298/csis0802119d.

Full text
Abstract:
To be a debugger is a good thing! Since the very beginning of the programming activity, debuggers are the most important and widely used tools after editors and compilers; we completely recognize their importance for software development and testing. Debuggers work at machine level, after the compilation of the source program; they deal with assembly, or binary-code, and are mainly data structure inspectors. ALMA is a program animator based on its abstract representation. The main idea is to show the algorithm being implemented by the program, independently from the language used to implement it. To say that ALMA is a debugger, with no value added, is not true! ALMA is a source code inspector but it deals with programming concepts instead of machine code. This makes possible to understand the source program at a conceptual level, and not only to fix run time errors. In this paper we compare our visualizer/animator system, ALMA, with one of the most well-known and used debuggers, the graphical version of GDB, the DDD program. The aim of the paper is twofold: the immediate objective is to prove that ALMA provides new features that are not usually offered by debuggers; the main contribution is to recall the concepts of debugger and animator, and clarify the role of both tools in the field of program understanding, or program comprehension. .
APA, Harvard, Vancouver, ISO, and other styles
2

Tolmach, Andrew, and Andrew W. Appel. "A Debugger for Standard ML." Journal of Functional Programming 5, no. 2 (April 1995): 155–200. http://dx.doi.org/10.1017/s0956796800001313.

Full text
Abstract:
AbstractWe have built a portable, instrumentation-based, replay debugger for the Standard ML of New Jersey compiler. Traditional ‘source-level’ debuggers for compiled languages actually operate at machine level, which makes them complex, difficult to port, and intolerant of compiler optimization. For secure languages like ML, however, debugging support can be provided without reference to the underlying machine, by adding instrumentation to program source code before compilation. Because instrumented code is (almost) ordinary source, it can be processed by the ordinary compiler. Our debugger is thus independent from the underlying hardware and runtime system, and from the optimization strategies used by the compiler. The debugger also provides reverse execution, both as a user feature and an internal mechanism. Reverse execution is implemented using a checkpoint and replay system; checkpoints are represented primarily by first-class continuations.
APA, Harvard, Vancouver, ISO, and other styles
3

Chiş, Andrei, Marcus Denker, Tudor Gîrba, and Oscar Nierstrasz. "Practical domain-specific debuggers using the Moldable Debugger framework." Computer Languages, Systems & Structures 44 (December 2015): 89–113. http://dx.doi.org/10.1016/j.cl.2015.08.005.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Dolinay, Jan, Petr Dostalek, and Vladimir Vasek. "Arduino Debugger." IEEE Embedded Systems Letters 8, no. 4 (December 2016): 85–88. http://dx.doi.org/10.1109/les.2016.2619692.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Neville-Neil, George V. "Getting Off the Mad Path." Queue 19, no. 6 (December 31, 2021): 18–21. http://dx.doi.org/10.1145/3511662.

Full text
Abstract:
KV continues to grind his teeth as he sees code loaded with debugging statements that would be totally unnecessary if the programmers who wrote the code could be both confident in and proficient with their debuggers. If one is lucky enough to have access to a good debugger, one should give extreme thanks to whatever they normally give thanks to and use the damn thing!
APA, Harvard, Vancouver, ISO, and other styles
6

Lanese, Ivan, Adrián Palacios, and Germán Vidal. "Causal-Consistent Replay Reversible Semantics for Message Passing Concurrent Programs." Fundamenta Informaticae 178, no. 3 (January 15, 2021): 229–66. http://dx.doi.org/10.3233/fi-2021-2005.

Full text
Abstract:
Causal-consistent reversible debugging is an innovative technique for debugging concurrent systems. It allows one to go back in the execution focusing on the actions that most likely caused a visible misbehavior. When such an action is selected, the debugger undoes it, including all and only its consequences. This operation is called a causal-consistent rollback. In this way, the user can avoid being distracted by the actions of other, unrelated processes. In this work, we introduce its dual notion: causal-consistent replay. We allow the user to record an execution of a running program and, in contrast to traditional replay debuggers, to reproduce a visible misbehavior inside the debugger including all and only its causes. Furthermore, we present a unified framework that combines both causal-consistent replay and causal-consistent rollback. Although most of the ideas that we present are rather general, we focus on a popular functional and concurrent programming language based on message passing: Erlang.
APA, Harvard, Vancouver, ISO, and other styles
7

Von Kaenel, Pierre A. "A debugger tutorial." ACM SIGCSE Bulletin 19, no. 4 (December 1987): 40–44. http://dx.doi.org/10.1145/39316.39325.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Ramsey, Norman, and David R. Hanson. "A retargetable debugger." ACM SIGPLAN Notices 27, no. 7 (July 1992): 22–31. http://dx.doi.org/10.1145/143103.143112.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Bowman, Dick, and Jim Weigang. "StepView APL Debugger." ACM SIGAPL APL Quote Quad 22, no. 4 (June 1992): 8–9. http://dx.doi.org/10.1145/140660.140671.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Rafieymehr, Ali, and Richard McKeever. "Java visual debugger." ACM SIGCSE Bulletin 39, no. 2 (June 2007): 75–79. http://dx.doi.org/10.1145/1272848.1272889.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Debugger"

1

Pope, Bernard James. "A declarative debugger for Haskell /." Connect to thesis, 2006. http://eprints.unimelb.edu.au/archive/00003290.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Johnson, Stephen Lee. "TeaBag: A Debugger for Curry." PDXScholar, 2004. https://pdxscholar.library.pdx.edu/open_access_etds/2663.

Full text
Abstract:
This thesis describes TeaBag, which is a debugger for functional logic computations. TeaBag is an accessory of a virtual machine currently under development. A distinctive feature of this machine is its operational completeness of computations, which places novel demands on a debugger. This thesis describes the features of TeaBag, in particular the handling of non-determinism, the ability to control nondeterministic steps, to remove context information, to toggle eager evaluation, and to set breakpoints on both functions and terms. This thesis also describes TeaBag's architecture and its interaction with the associated virtual machine. Finally, some debugging sessions of defective programs are presented to demonstrate TeaBag's ability to locate bugs. A distinctive feature of TeaBag is how it presents non-deterministic trace steps of an expression evaluation trace to the user. In the past expression evaluation traces were linearized via backtracking. However, the presence of backtracking makes linear traces difficult to follow. TeaBag does not present backtracking to the user. Rather TeaBag presents the trace in two parts. One part is the search space which has a tree structure and the other part is a linear sequence of steps for one path through the search space.
APA, Harvard, Vancouver, ISO, and other styles
3

Schütze, Lars. "Implementing a Debugger for Dresden OCL." Bachelor's thesis, Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2013. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-118599.

Full text
Abstract:
Although originally designed as an extension for the Unifi ed Modeling Language (UML), today, the Object Constraint Language (OCL) has been broadly adopted in the context of both UML and other modeling and domain-specifi c languages. However, appropriate tooling, supporting modelers and software developers on using OCL is still scarce and lacks important features such as debugging support. As OCL constraints are likely to become rather complex for real world examples, it is hard to comprehend the in uence of single OCL expressions and subexpressions on the result of a completely evaluated OCL constraint in the context of speci fic constrained objects. Therefore, debugging is of topmost importance for both constraint comprehension and maintenance. Thus, the major task of this work is to develop a graphical debugger integrated into Dresden OCL and the Eclipse Integrated Development Environment (IDE) to fill this gap.
APA, Harvard, Vancouver, ISO, and other styles
4

Wagner, Christina. "Anforderungen an einen Debugger für Softwaregeneratoren." Bachelor's thesis, Universitätsbibliothek Leipzig, 2016. http://nbn-resolving.de/urn:nbn:de:bsz:15-qucosa-202633.

Full text
Abstract:
Eine wichtige Aufgabe bei der Softwareentwicklung ist das Auffinden von Fehlern und das Verstehen ihrer Ursachen. Zur Unterstützung dieser Aufgabe gibt es zahlreiche De-bugger. Bei der Nutzung von Softwaregeneratoren benötigt man zum Debuggen spezielle Informationen. In dieser Arbeit werden Anforderungen an einen Debugger für Software-generatoren definiert. Dazu werden zunächst strukturell ähnliche Softwaregeneratoren auf ihre Debugger untersucht und grundsätzliche Debuggertypen identifiziert. Aus diesen werden 15 Anforderungen formuliert, die der hier beispielhaft betrachtete Softwaregener-ator erfüllen soll. Anschließend erfolgen eine Verallgemeinerung der Ergebnisse und eine kurze Diskussion der Umsetzung auf der Plattform JetBrains MPS.
APA, Harvard, Vancouver, ISO, and other styles
5

Chelliah, M. "A Compiler and Symbolic Debugger for Occam." Thesis, Indian Institute of Science, 1989. http://hdl.handle.net/2005/77.

Full text
Abstract:
We have implemented Occam, a parallel programming language, on a uniprocessor machine (MC-68020 based HORIZON I11 running on UNIX system V.2) with simulated concurrency. Occam is a descendant of CSP with a few convenient modifications like channels used for communication and procedures. Two additions to the original language, i.e., output guards and recursion have been proposed. Front end of the compiler was developed using LEX and YACC. An innovative code generator, generator based on tree pattern matching has been used to generate the back end of the compiler, which generates efficient MC-68020 assembly code. A kernel for process administration is the runtime support provided. It has been developed entirely in ' C ' and made available as a library. This is linked with the assembly module to generate the executable version of the input Occam program. We have also interfaced our Occam compiler with Unix system V.2 source level debugger 'Sdb' so as to provide debugging support for Occam programmers. Issues involved in parallel debugging have been investigated and those demanding minimum effort have been incorporated in Occam debugger by modifying the runtime support of the uniprocessor implementation. Modifications to the uniprocessor implementation so as to make it run on a shared memory multiprocessor machine(HCL MAGNUM-P with four MC-68030 processors) are also discussed. The support provided by MAGNUM-P at the architecture and operating system levels is explained in detail. Our Occam compiler for the multiprocessor generates code, but the generated code has not been tested since the machine is not yet ready.
APA, Harvard, Vancouver, ISO, and other styles
6

Ni, Wayland 1982. "WSIM configurable digital signal processor simulator/debugger." Thesis, Massachusetts Institute of Technology, 2004. http://hdl.handle.net/1721.1/16683.

Full text
Abstract:
Thesis (M. Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2004.
Includes bibliographical references (leaf 53).
This electronic version was submitted by the student author. The certified thesis is available in the Institute Archives and Special Collections.
This M.Eng. Thesis presents a design and implementation of a full-featured configurable Digital Signal Processor (DSP) simulator/debugger. The user will be able to set configurations in order to model a specific architecture design. The simulator will have a command interpreter to listen to and process commands given by the user. When supplied with an assembly program, the simulator will allow the user to step through the execution of the program cycle by cycle, as well as calculate statistics like instruction, resource, and cache profiling. Some of the main features of the simulator are a multiply-accumulate unit, memory with direct and indirect offset addressing, and loop instructions.
by Wayland Ni.
M.Eng.
APA, Harvard, Vancouver, ISO, and other styles
7

Markusson, Christoffer. "Implementation of an application debugger for software in embedded systems." Thesis, Linköping University, Department of Computer and Information Science, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-15539.

Full text
Abstract:

Debugging applications that are running in embedded systems is becoming harder and harder due to the growing complexity of the systems. This is especially true for embedded systems that are developed for the automotive market.

To aid the debugging there are tools called debuggers. Historically, debuggers have been implemented by using a debug port to connect a software debugger running at the developer machine to dedicated on-chip debugging hardware. The problem with this approach is that it is expensive and that it is not possible to use it if the debug port on the system is not available.Therefore there is a demand for user-friendly debuggers that are not as expensive and require no extra hardware.

This report presents alternatives to debugging embedded systems. From these alternatives a completely software based debugger solution called monitor-based debugging is selected and acts as a foundation for an implementation that is described in the report. The implementation uses GNU Debugger (GDB) and its remote debugging capabilities to perform debugging.

The implemented debugger is evaluated by using it to debug applications that are running in a powertrain control unit in a modern truck. It is also compared to two commercial hardware based debuggers. In the evaluation it is found that the debugger functionalities and user-friendliness are on par with the commercial alternatives, but that it lacks some in its non-intrusive capabilities when comparing it with the high-end alternatives on the market.

APA, Harvard, Vancouver, ISO, and other styles
8

Nilsson, Sverker. "Heapy: A Memory Profiler and Debugger for Python." Thesis, Linköping University, Department of Computer and Information Science, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-7247.

Full text
Abstract:

Excessive memory use may cause severe performance problems and system crashes. Without appropriate tools, it may be difficult or impossible to determine why a program is using too much memory. This applies even though Python provides automatic memory management --- garbage collection can help avoid many memory allocation bugs, but only to a certain extent due to the lack of information during program execution. There is still a need for tools helping the programmer to understand the memory behaviour of programs, especially in complicated situations. The primary motivation for Heapy is that there has been a lack of such tools for Python.

The main questions addressed by Heapy are how much memory is used by objects, what are the objects of most interest for optimization purposes, and why are objects kept in memory. Memory leaks are often of special interest and may be found by comparing snapshots of the heap population taken at different times. Memory profiles, using different kinds of classifiers that may include retainer information, can provide quick overviews revealing optimization possibilities not thought of beforehand. Reference patterns and shortest reference paths provide different perspectives of object access patterns to help explain why objects are kept in memory.

APA, Harvard, Vancouver, ISO, and other styles
9

Manoh, Nadia, and Hamoud Abdullah. "Software debugging using the debugger SAM4E Xplained Pro." Thesis, Malmö universitet, Fakulteten för teknik och samhälle (TS), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:mau:diva-20090.

Full text
Abstract:
Inbyggda system finns i nästan alla enheter som används i vårt dagliga liv, som exempelvis mobiltelefoner, kylskåp och bilar. En del enheter kan vara betydligt känsligare än andra, vilket innebär att en bugg som existerar i ett system kan orsaka skada, till och med förlust av människoliv, eller orsakar ingen skada alls. Mjukvarutestning och mjukvarufelsökning genomförs för att reducera buggar i ett system.Utbildningsprogrammet Datateknik och Mobil IT på Malmö universitet fokuserar inte på att undervisa mjukvarufelsökning med hjälp av felsökningsverktyg. Således presenterar denna forskning en felsökningslaboration skapat för studenter som går Datateknik och Mobil IT, som anses hjälpa studenterna att få kunskap i hur man använder felsökningsverktyget SAM4E Xplained Pro för att lokalisera buggar. Som ett resultat, utfördes felsökningslaborationen av fyra studenter varav 75 procent av buggarna hittades och åtgärdades.
Embedded systems are found in almost every device used in our daily lives, including cell phones, refrigerators, and cars. Some devices may be significantly more sensitive than others, meaning a bug appearing in a system could cause harm, even loss of human lives or cause no harm at all. To reduce bugs in a system, software testing and software debugging are performed.The Computer Science program at Malmö University does not focus on teaching software debugging using a debugger. Thus, this thesis presents a debugging lab created for Computer Science students, considered to help them gain knowledge in how to use the debugger SAM4E Xplained Pro to locate bugs. As a result, four students performed the debugging lab of which 75 percent of the bugs were found and remedied.
APA, Harvard, Vancouver, ISO, and other styles
10

Watson, Gregory R. (Gregory Richard). "The design and implementation of a parallel relative debugger." Monash University, School of Computer Science and Software Engineering, 2000. http://arrow.monash.edu.au/hdl/1959.1/8772.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Debugger"

1

Swan, Tom. Mastering Turbo debugger. Carmel, Ind., USA: Hayden Books, 1990.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Perl Debugger: Pocket Reference. Beijing: O'Reilly, 2004.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

S, Norsk Data A. Symbolic debugger user guide. [Oslo]: Norsk Data A. S., 1986.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Wang, Chang Jian. An intelligent concurrent debugger system. Ottawa: National Library of Canada = Bibliothèque nationale du Canada, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Company, Hewlett-Packard. HP Symbolic Debugger user's guide. 4th ed. Cupertino: Hewlett-Packard, 1987.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Cooper, R. C. B. Pilgrim: A debugger for distributed systems. Cambridge: University of Cambridge, Computer Laboratory, 1987.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Olsen, J. W. Presenting SoftICE: The advanced Windows debugger. Foster City, CA: IDG Book Worldwide, 1996.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Instruments, Texas. TMS320C3X C source debugger: User's guide. [S.l.]: Texas Instruments, 1993.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Pancake, Cherri M. Debugger visualizations for shared-memory multiprocessors. Ithaca, N.Y: Cornell Theory Center, Cornell University, 1991.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Instruments, Texas. TMS320C4X C source debugger: User's guide. [S.l.]: Texas Instruments, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Debugger"

1

Weik, Martin H. "debugger." In Computer Science and Communications Dictionary, 367. Boston, MA: Springer US, 2000. http://dx.doi.org/10.1007/1-4020-0613-6_4472.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Kohls, Christian, Alexander Dobrynin, and Florian Leonhard. "Debugger." In Programmieren lernen mit Kotlin, 287–89. München: Carl Hanser Verlag GmbH & Co. KG, 2020. http://dx.doi.org/10.3139/9783446467118.023.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Blunden, Bill. "Debugger Internals." In Software Exorcism: A Handbook for Debugging and Optimizing Legacy Code, 157–213. Berkeley, CA: Apress, 2012. http://dx.doi.org/10.1007/978-1-4302-5108-8_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Blunden, Bill. "Debugger Internals." In Software Exorcism: A Handbook for Debugging and Optimizing Legacy Code, 157–213. Berkeley, CA: Apress, 2003. http://dx.doi.org/10.1007/978-1-4302-0788-7_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Hering, Ekbert, and Alexander Mendler. "Debuggen mit dem Turbo Debugger unter Windows." In Das Vieweg Buch zu Turbo Pascal für Windows, 177–95. Wiesbaden: Vieweg+Teubner Verlag, 1992. http://dx.doi.org/10.1007/978-3-322-91760-7_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Vraný, Jan, and Michal Píše. "Multilanguage Debugger Architecture." In SOFSEM 2010: Theory and Practice of Computer Science, 731–42. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-11266-9_61.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Bontekoe, Tj Romke, and Do Kester. "Memsys as Debugger." In Maximum Entropy and Bayesian Methods, 235–40. Dordrecht: Springer Netherlands, 1992. http://dx.doi.org/10.1007/978-94-017-2219-3_17.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Van Hoey, Jo. "Data Display Debugger." In Beginning x64 Assembly Programming, 51–55. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-5076-1_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Reps, Thomas W., and Tim Teitelbaum. "The SSL Debugger." In The Synthesizer Generator Reference Manual, 112–14. New York, NY: Springer New York, 1989. http://dx.doi.org/10.1007/978-1-4613-9633-8_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Reiss, Steven P. "The FIELD Debugger." In The Field Programming Environment: A Friendly Integrated Environment for Learning and Development, 53–79. Boston, MA: Springer US, 1995. http://dx.doi.org/10.1007/978-1-4615-2215-7_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Debugger"

1

In-geol Chun and Chae-deok Lim. "NanoEsto Debugger: The Tiny Embedded System Debugger." In 8th International Conference on Advanced Communication Technology. IEEE, 2006. http://dx.doi.org/10.1109/icact.2006.206065.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Ramsey, Norman, and David R. Hanson. "A retargetable debugger." In the ACM SIGPLAN 1992 conference. New York, New York, USA: ACM Press, 1992. http://dx.doi.org/10.1145/143095.143112.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Cuny, Janice, George Forman, Alfred Hough, Joydip Kundu, Calvin Lin, Lawrence Snyder, and David Stemple. "The Ariadne debugger." In the 1993 ACM/ONR workshop. New York, New York, USA: ACM Press, 1993. http://dx.doi.org/10.1145/174266.174276.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Chun, In-geol, Choon-oh Lee, and Duk-kyun Woo. "Esto NS-Debugger: The Non-stop Debugger for Embedded Systems." In The 9th International Conference on Advanced Communication Technology. IEEE, 2007. http://dx.doi.org/10.1109/icact.2007.358386.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Ingeol Chun and Chaedeok Lim. "ES-debugger : the flexible embedded system debugger based on JTAG technology." In The 7th International Conference on Advanced Communication Technology. IEEE, 2005. http://dx.doi.org/10.1109/icact.2005.246099.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Lumetta, Steven S., and David E. Culler. "The Mantis parallel debugger." In the SIGMETRICS symposium. New York, New York, USA: ACM Press, 1996. http://dx.doi.org/10.1145/238020.238056.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Bertot, Yves. "Occurrences in debugger specifications." In the ACM SIGPLAN 1991 conference. New York, New York, USA: ACM Press, 1991. http://dx.doi.org/10.1145/113445.113473.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Duca, Nat, Chris Niski, Jonathan Bilodeau, Yuan Chen, Matthew Bolitho, and Jonathan Cohen. "Building a graphics debugger." In ACM SIGGRAPH 2005 Sketches. New York, New York, USA: ACM Press, 2005. http://dx.doi.org/10.1145/1187112.1187127.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Song, Myoungkyu, and Eli Tilevich. "The anti-goldilocks debugger." In Proceeding of the 24th ACM SIGPLAN conference companion. New York, New York, USA: ACM Press, 2009. http://dx.doi.org/10.1145/1639950.1640027.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Chiş, Andrei, Oscar Nierstrasz, and Tudor Gîrba. "Towards a moldable debugger." In the 7th Workshop. New York, New York, USA: ACM Press, 2013. http://dx.doi.org/10.1145/2489798.2489801.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Debugger"

1

Miller, P., D. Nessett, and R. Pizzi. GNU debugger internal architecture. Office of Scientific and Technical Information (OSTI), December 1993. http://dx.doi.org/10.2172/10123120.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Doubleday, Dennis L. The Durra Application Debugger/Monitor. Fort Belvoir, VA: Defense Technical Information Center, September 1989. http://dx.doi.org/10.21236/ada219290.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Johnson, Stephen. TeaBag: A Debugger for Curry. Portland State University Library, January 2000. http://dx.doi.org/10.15760/etd.2658.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Tsien, Christine L. Maygen: A Symbolic Debugger Generation System. Fort Belvoir, VA: Defense Technical Information Center, July 1993. http://dx.doi.org/10.21236/ada272512.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Burns, T. J. ORGBUG -- A windows-based combinatorial geometry debugger. Office of Scientific and Technical Information (OSTI), June 1993. http://dx.doi.org/10.2172/7368450.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Burns, T. J. ORGBUG -- A windows-based combinatorial geometry debugger. Office of Scientific and Technical Information (OSTI), June 1993. http://dx.doi.org/10.2172/10170388.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Baskerville, David B. Graphic Presentation of Data Structures in the DBX Debugger. Fort Belvoir, VA: Defense Technical Information Center, July 1985. http://dx.doi.org/10.21236/ada611773.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Wolfe, M. Purple L1 Milestone Review Panel TotalView Debugger Functionality and Performance for ASC Purple. Office of Scientific and Technical Information (OSTI), December 2006. http://dx.doi.org/10.2172/896623.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Debugger' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography