| podobné slovo | definícia |
debugger
(mass) | debugger
- debugger, ladiaci program |
debugger
(msas) | debugger
- debugger |
debugger
(msasasci) | debugger
- debugger |
debugged
(encz) | debugged,odladěný např. program Zdeněk Brož |
debugger
(encz) | debugger,debugger n: Zdeněk Broždebugger,ladící program Zdeněk Brož |
debuggers
(encz) | debuggers,ladící programy Zdeněk Brož |
debugging
(encz) | debugging,ladění n: Zdeněk Broždebugging,odstraňování chyb v: např. při programování Martin Ligač |
debugger
(czen) | debugger,debuggern: Zdeněk Brož |
debugger
(wn) | debugger
n 1: a program that helps in locating and correcting programming
errors |
debugger
(foldoc) | debugger
debugging tool
A tool used by a programmer to monitor
and control a program he is trying to fix. The most important
functions of a debugger are tracing, stepping, breakpoints and
watches.
Tracing displays a step-by-step report on what statement the
program is currently executing, allowing the programmer to follow
the flow of control through if statements, loops (loop),
subroutine calls, etc.
Breakpoints and watches both pause execution of the program
and return control to the debugger under certain conditions. A
breakpoint triggers when execution reaches a particular
statement in the program and a watch triggers whenever a
specific variable is modified. Stepping is like a breakpoint on
every statement, often with the option to step "into" or "over" a
subroutine, i.e. continue stepping through the statements of the
subroutine or just execute it without pausing and resume stepping
when it returns.
Whenever control returns to the debugger it lets the programmer
ask to see the values of variables, and possibly modify them,
before resuming execution. Some debuggers can be set to
automatically perform some action like display a variable value
and resume.
A debugger can interact with the target program in different ways.
Some debuggers require the program to be loaded into the debugger
which may then modify or "instrument" the program for debugging.
Others can "attach" to a program that is already running. Some
are built into the normal program execution environment (e.g. an
interpreter) and can be set to run under certain conditions,
e.g. errors.
Early debuggers such as Unix's adb only knew about the
compiled executable code so sometimes debugging had to be done at
the level of machine code instructions and numerical memory
locations. If you were lucky, the debugger could access the
program's symbol table and display the original names of
subroutines and variables. Sometimes this required the program to
be "compiled for debugging". Since compiling every program for
debugging would add significantly to the size of a distribution
of a whole operating system, it is common for programs to be
distributed without debugging support but for individual programs
to be made available with it.
A major advance in debuggers was source-level debugging. This
gives the programmer a view of their source code annotated with
breakpoints and a pointer to the statement currently being
executed. Such a view is commonly part of an {integrated
development environment} like Visual Basic.
(2014-08-23)
|
debugging
(foldoc) | debugging
The process of attempting to determine the cause of
the symptoms of malfunctions in a program or other system. These
symptoms may be detected during testing or use by real users.
Symptoms are often caused by factors outside the program, such as
misconfiguration of the user's operating system,
misunderstanding by the user (see PEBCAK) or failures in other
external systems on which the program relies. Some of these are
more in the realm of technical support but need to be
eliminated. Debugging really starts when it has been established
that the program is not behaving according to its specification
(which may be formal or informal). It can be done by visual
inspection of the source code, debugging by printf or using a
debugger. The result may be that the program is actually
behaving as specified but that the spec is wrong or the
requirements on which it was based were deficient in some way (see
BAD).
Once a bug has been identified and a fix applied, the program must
be tested to determine whether the bug is really fixed and what
effects the changes have had on other aspects of the program's
operation (see regression testing).
The term is said to have been coined by Grace Hopper, based on
the term "bug".
(2006-11-27)
|
debugging an empty file
(foldoc) | debugging an empty file
A humourous definition of programming
that considers a complete absence of any code as a bug to be
fixed.
test-driven development proceeds by the programmer writing
tests for code that doesn't exist yet, which could be
described as testing an empty file.
(2012-05-01)
|
debugging by printf
(foldoc) | debugging by printf
The debugging technique where the programmer
inserts print statements into a program so that when run the
program leaves a "trail of breadcrumbs" allowing him to see
which parts were executed. The information output may just be
a short string to indicate that a particular point in the code
has been reached or it might be a complete stack trace. The
output typically just goes to the window or terminal in which
the program is running or may be written to a log file.
printf is the standard C print function, other languages
would use different names.
(2007-03-08)
|
debugging tool
(foldoc) | debugger
debugging tool
A tool used by a programmer to monitor
and control a program he is trying to fix. The most important
functions of a debugger are tracing, stepping, breakpoints and
watches.
Tracing displays a step-by-step report on what statement the
program is currently executing, allowing the programmer to follow
the flow of control through if statements, loops (loop),
subroutine calls, etc.
Breakpoints and watches both pause execution of the program
and return control to the debugger under certain conditions. A
breakpoint triggers when execution reaches a particular
statement in the program and a watch triggers whenever a
specific variable is modified. Stepping is like a breakpoint on
every statement, often with the option to step "into" or "over" a
subroutine, i.e. continue stepping through the statements of the
subroutine or just execute it without pausing and resume stepping
when it returns.
Whenever control returns to the debugger it lets the programmer
ask to see the values of variables, and possibly modify them,
before resuming execution. Some debuggers can be set to
automatically perform some action like display a variable value
and resume.
A debugger can interact with the target program in different ways.
Some debuggers require the program to be loaded into the debugger
which may then modify or "instrument" the program for debugging.
Others can "attach" to a program that is already running. Some
are built into the normal program execution environment (e.g. an
interpreter) and can be set to run under certain conditions,
e.g. errors.
Early debuggers such as Unix's adb only knew about the
compiled executable code so sometimes debugging had to be done at
the level of machine code instructions and numerical memory
locations. If you were lucky, the debugger could access the
program's symbol table and display the original names of
subroutines and variables. Sometimes this required the program to
be "compiled for debugging". Since compiling every program for
debugging would add significantly to the size of a distribution
of a whole operating system, it is common for programs to be
distributed without debugging support but for individual programs
to be made available with it.
A major advance in debuggers was source-level debugging. This
gives the programmer a view of their source code annotated with
breakpoints and a pointer to the statement currently being
executed. Such a view is commonly part of an {integrated
development environment} like Visual Basic.
(2014-08-23)
|
portable scheme debugger
(foldoc) | Portable Scheme Debugger
(PSD) A package for source code debugging of R4RS-compliant
Scheme under GNU Emacs by Kellom ?ki Pertti
. Version 1.1. Distributed under GNU GPL.
It works with scm, Elk and Scheme->C.
(ftp://ftp.cs.tut.fi/pub/src/languages/schemes/psd.tar.Z).
(1992-10-08)
|
rotary debugger
(foldoc) | rotary debugger
(Commodore) Essential equipment for those late-night or
early-morning debugging sessions. Mainly used as sustenance
for the hacker. Comes in many decorator colours, such as
Sausage, Pepperoni, and Garbage.
(1995-01-11)
|
shotgun debugging
(foldoc) | shotgun debugging
The software equivalent of Easter egging; the making of
relatively undirected changes to software in the hope that a
bug will be perturbed out of existence. This almost never
works, and usually introduces more bugs.
[Jargon File]
|
source-level debugger
(foldoc) | source-level debugger
A debugger that shows the programmer the
line or expression in the source code that resulted in a
particular machine code instruction of a running program
loaded in memory. This helps the programmer to analyse a
program's behaviour in the high-level terms like source-level
flow control constructs, procedure calls, named
variables, etc instead of machine instructions and memory
locations. Source-level debugging also makes it possible to
step through execution a line at a time and set source-level
breakpoints.
In order to support source-level debugging, the program must
be compiled with this option enabled so that extra information
is included in the executable code to identify the
corresponding positions in the source code.
A symbolic debugger is one level lower - it displays symbols
(procedure and variable names) stored in the executable but
not individual source code lines.
GDB is a widely used example of a source-level debugger.
(2007-04-03)
|
tcl-debug
(foldoc) | tcl-debug
A debugger for Tcl by Don Libes that
can be easily embedded in other applications. It is included
with many other Tcl libraries.
(ftp://ftp.cme.nist.gov/pub/expect/tcl-debug.tar.Z).
(1994-10-31)
|
turbo debugger
(foldoc) | Turbo Debugger
A source-level debugger designed for use with
Borland and other compilers.
(http://borland.com/).
(1999-04-23)
|
universal debugger
(foldoc) | Universal Debugger
udb
(udb) KSR's interactive {source level
debugger} for serial and parallel programs written in KSR,
Fortran, KSR C and KSR1 assembly language.
Udb is a source level debugger for testing and debugging
serial and parallel programs; it is compatible with GDB and
dbx. The user can direct udb either by typing commands or
graphically through an X-based window interface; the latter
provides simultaneous display of source code, I/O and
instructions. For parallel programs, operations can be
carried out per-thread.
{Home
(http://tc.cornell.edu/Parallel.Tools/tools/udb.html)}.
(1995-05-07)
|
rotary debugger
(jargon) | rotary debugger
n.
[Commodore] Essential equipment for those late-night or early-morning
debugging sessions. Mainly used as sustenance for the hacker. Comes in many
decorator colors, such as Sausage, Pepperoni, and Garbage. See {ANSI
standard pizza}.
|
shotgun debugging
(jargon) | shotgun debugging
n.
The software equivalent of Easter egging; the making of relatively
undirected changes to software in the hope that a bug will be perturbed out
of existence. This almost never works, and usually introduces more bugs.
|