Log in

Relevant bibliographies by topics / Debugger / Journal articles

To see the other types of publications on this topic, follow the link: Debugger.

Journal articles 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 top 50 journal articles for your research 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.

Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.

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

11

Cuny, Janice, George Forman, Alfred Hough, Joydip Kundu, Calvin Lin, Lawrence Snyder, and David Stemple. "The Ariadne debugger." ACM SIGPLAN Notices 28, no. 12 (December 1993): 85–95. http://dx.doi.org/10.1145/174267.174276.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

NILSSON, HENRIK. "How to look busy while being as lazy as ever: the Implementation of a lazy functional debugger." Journal of Functional Programming 11, no. 6 (November 2001): 629–71. http://dx.doi.org/10.1017/s095679680100418x.

Full text

Abstract:

This article describes the implementation of a debugger for lazy functional languages like Haskell. The key idea is to construct a declarative trace which hides the operational details of lazy evaluation. However, to avoid excessive memory consumption, the trace is constructed one piece at a time, as needed during a debugging session, by automatic re-execution of the program being debugged. The article gives a fairly detailed account of both the underlying ideas and of our implementation, and also presents performance figures which demonstrate the feasibility of the approach.

APA, Harvard, Vancouver, ISO, and other styles

13

Bertot, Yves. "Occurrences in debugger specifications." ACM SIGPLAN Notices 26, no. 6 (June 1991): 327–37. http://dx.doi.org/10.1145/113446.113473.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

SOSIČ, ROK, and DAVID ABRAMSON. "Guard: A Relative Debugger." Software: Practice and Experience 27, no. 2 (February 1997): 185–206. http://dx.doi.org/10.1002/(sici)1097-024x(199702)27:2<185::aid-spe79>3.0.co;2-d.

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

HANSON, DAVID R., and MUKUND RAGHAVACHARI. "A Machine-Independent Debugger." Software: Practice and Experience 26, no. 11 (November 1996): 1277–99. http://dx.doi.org/10.1002/(sici)1097-024x(199611)26:11<1277::aid-spe62>3.0.co;2-y.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

Isoda, S., T. Shimomura, and Y. Ono. "VIPS: A Visual Debugger." IEEE Software 4, no. 3 (May 1987): 8–19. http://dx.doi.org/10.1109/ms.1987.230394.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Pourheidari, Mohammad, Robert R. Kessler, and Harold Carr. "Moped (a portable debugger)." Lisp and Symbolic Computation 3, no. 1 (January 1990): 39–65. http://dx.doi.org/10.1007/bf01806125.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Bao, D., D. L. Carni, L. De Vito, and L. Tomaciello. "Session Initiation Protocol Automatic Debugger." IEEE Transactions on Instrumentation and Measurement 58, no. 6 (June 2009): 1869–77. http://dx.doi.org/10.1109/tim.2008.2005078.

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

Cargill, Thomas A. "Implementation of the blit debugger." Software: Practice and Experience 15, no. 2 (February 1985): 153–68. http://dx.doi.org/10.1002/spe.4380150204.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Gait, Jason. "A debugger for concurrent programs." Software: Practice and Experience 15, no. 6 (June 1985): 539–54. http://dx.doi.org/10.1002/spe.4380150603.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Griffin, James H., Harvey J. Wasserman, and Lauren P. McGavran. "A debugger for parallel processes." Software: Practice and Experience 18, no. 12 (December 1988): 1179–90. http://dx.doi.org/10.1002/spe.4380181206.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Side, R. S., and G. C. Shoja. "A debugger for distributed programs." Software: Practice and Experience 24, no. 5 (May 1994): 507–25. http://dx.doi.org/10.1002/spe.4380240506.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Hanson, David R. "A machine-independent debugger ? revisited." Software: Practice and Experience 29, no. 10 (August 1999): 849–62. http://dx.doi.org/10.1002/(sici)1097-024x(199908)29:10<849::aid-spe260>3.0.co;2-t.

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

Kellomäki, Pertti. "PSD—a portable scheme debugger." ACM SIGPLAN Lisp Pointers VI, no. 1 (January 2, 1993): 15–23. http://dx.doi.org/10.1145/173770.173772.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

Brindle, A. F., R. N. Taylor, and D. F. Martin. "A debugger for Ada tasking." IEEE Transactions on Software Engineering 15, no. 3 (March 1989): 293–304. http://dx.doi.org/10.1109/32.21757.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

Boothe, Bob. "A fully capable bidirectional debugger." ACM SIGSOFT Software Engineering Notes 25, no. 1 (January 2000): 36–37. http://dx.doi.org/10.1145/340855.340867.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Elshoff, I. J. P. "A distributed debugger for Amoeba." ACM SIGPLAN Notices 24, no. 1 (January 3, 1989): 1–10. http://dx.doi.org/10.1145/69215.69216.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Heymann, Jurgen. "A 100% portable inline-debugger." ACM SIGPLAN Notices 28, no. 9 (September 1993): 39–46. http://dx.doi.org/10.1145/165364.165380.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

BANYASAD, OMID, and PHILIP T. COX. "DESIGN AND IMPLEMENTATION OF AN EDITOR/INTERPRETER FOR A VISUAL LOGIC PROGRAMMING LANGUAGE." International Journal of Software Engineering and Knowledge Engineering 23, no. 06 (August 2013): 801–38. http://dx.doi.org/10.1142/s0218194013500216.

Full text

Abstract:

The design and implementation of a programming environment including an editor, a debugger and an interpreter engine for Lograph, a general-purpose visual logic programming language, is discussed. The rationale for user-interface design decisions is presented, the goal of which is to increase cognitive support for the creation, exploration and debugging of Lograph programs. The design of the interpreter engine allows for animation of execution in the debugger. The engine takes full advantage of an efficient implementation of Prolog, and operates on a Prolog translation of Lograph programs and queries. The translated Lograph programs are probed with instrumentation code at appropriate places so that applications of Lograph rules are reported to the visual interface of the Lograph debugger as a side effect of the execution of a program.

APA, Harvard, Vancouver, ISO, and other styles

30

Wen, Hong Yuan. "Design of DSP Video Image Processing System Control Software." Advanced Materials Research 139-141 (October 2010): 2299–302. http://dx.doi.org/10.4028/www.scientific.net/amr.139-141.2299.

Full text

Abstract:

In order to realize the DSP Video Image Processing System works well in the highlight environment, the system control software is designed. In this control part, the ultra-low power MSP430 single chip microcomputer (MCU) is the core, which can be programmed to control the DSP Video Image Processing System, the video A/D converter and the highlight protection circuit by the Inter-Integrated Circuit (I2C) bus. The Image Processing algorithm models can be selected. Whether the highlight protection circuit is turned on or not depends on the comparison result of the environment light and the MCU light threshold. The control program code has been debugged and tested through the MSP development board and the IAR C-SPY debugger. The result shows the DSP Video Image Processing System Control Software is ideal.

APA, Harvard, Vancouver, ISO, and other styles

31

Bernstein, K. "Operational Semantics of a Focusing Debugger." Electronic Notes in Theoretical Computer Science 1, no. 1 (January 2004): 1–19. http://dx.doi.org/10.1016/s1571-0661(04)00002-7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

Bernstein, Karen L., and Eugene W. Stark. "Operational Semantics of a Focusing Debugger." Electronic Notes in Theoretical Computer Science 1 (1995): 13–31. http://dx.doi.org/10.1016/s1571-0661(04)80002-1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

Mauger, Claude, and Kevin Pammett. "An event-driven debugger for Ada." ACM SIGAda Ada Letters V, no. 2 (September 1985): 124–35. http://dx.doi.org/10.1145/324422.324387.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Smith, Edward T. "A debugger for message-based processes." Software: Practice and Experience 15, no. 11 (November 1985): 1073–86. http://dx.doi.org/10.1002/spe.4380151105.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Bovey, J. D. "A debugger for a graphical workstation." Software: Practice and Experience 17, no. 9 (September 1987): 647–62. http://dx.doi.org/10.1002/spe.4380170907.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Shu, William S. "Adapting a debugger for optimised programs." ACM SIGPLAN Notices 28, no. 4 (April 1993): 39–44. http://dx.doi.org/10.1145/152739.152744.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Yan, Song Y., and Lee Naish. "Completeness of an improved declarative debugger." Applied Mathematics Letters 4, no. 5 (1991): 7–12. http://dx.doi.org/10.1016/0893-9659(91)90134-h.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Tamir, Dan E., Ravi Ananthakrishnan, and Abraham Kandel. "A visual debugger for pure Prolog." Information Sciences - Applications 3, no. 2 (March 1995): 127–47. http://dx.doi.org/10.1016/1069-0115(94)00048-7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Sadeghi, Parissa H., and Frank Huch. "The Interactive Curry Observation Debugger iCODE." Electronic Notes in Theoretical Computer Science 177 (June 2007): 107–22. http://dx.doi.org/10.1016/j.entcs.2007.01.007.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

de la Encina, Alberto, Mercedes Hidalgo-Herrero, Luis Llana, and Fernando Rubio. "A Semantic Framework to Debug Parallel Lazy Functional Languages." Mathematics 8, no. 6 (May 26, 2020): 864. http://dx.doi.org/10.3390/math8060864.

Full text

Abstract:

It is not easy to debug lazy functional programs. The reason is that laziness and higher-order complicates basic debugging strategies. Although there exist several debuggers for sequential lazy languages, dealing with parallel languages is much harder. In this case, it is important to implement debugging platforms for parallel extensions, but it is also important to provide theoretical foundations to simplify the task of understanding the debugging process. In this work, we deal with the debugging process in two parallel languages that extend the lazy language Haskell. In particular, we provide an operational semantics that allows us to reason about our parallel extension of the sequential debugger Hood. In addition, we show how we can use it to analyze the amount of speculative work done by the processes, so that it can be used to optimize their use of resources.

APA, Harvard, Vancouver, ISO, and other styles

41

Rajotte, François, and Michel R. Dagenais. "Real-Time Linux Analysis Using Low-Impact Tracer." Advances in Computer Engineering 2014 (June 5, 2014): 1–8. http://dx.doi.org/10.1155/2014/173976.

Full text

Abstract:

Debugging real-time software presents an inherent challenge because of the nature of real-time itself. Traditional debuggers use breakpoints to stop the execution of a program and allow the inspection of its status. The interactive nature of a debugger is incompatible with the strict timing constraints of a real-time application. In order to observe the execution of a real-time application, it is therefore necessary to use a low-impact instrumentation solution. Tracing allows the collection of low-level events with minimal impact on the traced application. These low-level events can be difficult to use without appropriate tools. We propose an analysis framework to model real-time tasks from tracing data recovered using the LTTng tracer. We show that this information can be used to populate views and help developers discover interesting patterns and potential problems.

APA, Harvard, Vancouver, ISO, and other styles

42

Friburger, Nathalie, and Max Silberztein. "Quatrième Partie." Lingvisticæ Investigationes. International Journal of Linguistics and Language Resources 22, no. 1-2 (December 31, 1999): 399–412. http://dx.doi.org/10.1075/li.22.1-2.24fri.

Full text

Abstract:

intex system users have to describe linguistic facts with grammars written by the graph editor. When the number of graphs is important, finding and locating errors is a difficult task. In this article, we suggest a solution using a technique derived from computer science: debugging. To debug graphs, we offer an interface belonging to the intex system to help linguists in their works. We explain how we use Earley’s algorithm, borrowed from graph theory, to create the debugger and demonstrate the usefulness of this debugger for building graphs based on examples.

APA, Harvard, Vancouver, ISO, and other styles

43

SOMOGYI and HENDERSON. "The Implementation Technology of the Mercury Debugger." Electronic Notes in Theoretical Computer Science 30, no. 4 (April 2000): 1–20. http://dx.doi.org/10.1016/s1571-0661(05)01127-8.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

Somogyi, Zoltan, and Fergus Henderson. "The Implementation Technology of the Mercury Debugger." Electronic Notes in Theoretical Computer Science 30, no. 4 (April 2000): 256–75. http://dx.doi.org/10.1016/s1571-0661(05)80661-9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

May, John, and Francine Berman. "Retargetability and Extensibility in a Parallel Debugger." Journal of Parallel and Distributed Computing 35, no. 2 (June 1996): 142–55. http://dx.doi.org/10.1006/jpdc.1996.0077.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Sorel, P. E., M. G. Fernandez, and S. Ghosh. "A dynamic debugger for asynchronous distributed algorithms." IEEE Software 11, no. 1 (January 1994): 69–76. http://dx.doi.org/10.1109/52.251213.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

Caballero, R., N. Martí-Oliet, A. Riesco, and A. Verdejo. "A Declarative Debugger for Maude Functional Modules." Electronic Notes in Theoretical Computer Science 238, no. 3 (June 2009): 63–81. http://dx.doi.org/10.1016/j.entcs.2009.05.013.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Szűgyi, Zalán, István Forgács, and Zoltán Porkoláb. "4D Ariadne the Static Debugger of Java Programs." Periodica Polytechnica Electrical Engineering 55, no. 3-4 (2011): 127. http://dx.doi.org/10.3311/pp.ee.2011-3-4.05.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Sewry, D. A., P. G. Clayton, and E. P. Wentworth. "CCS specification of a Linda behavioural model debugger." IEE Proceedings - Software Engineering 144, no. 2 (1997): 89. http://dx.doi.org/10.1049/ip-sen:19970972.

Full text

APA, Harvard, Vancouver, ISO, and other styles

50

Caballero, Rafael, Enrique Martin-Martin, Adrián Riesco, and Salvador Tamarit. "A zoom-declarative debugger for sequential Erlang programs." Science of Computer Programming 110 (October 2015): 104–18. http://dx.doi.org/10.1016/j.scico.2015.06.011.

Full text

APA, Harvard, Vancouver, ISO, and other styles

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!