debugger - definition. What is debugger
Diclib.com
قاموس ChatGPT
أدخل كلمة أو عبارة بأي لغة 👆
اللغة:

ترجمة وتحليل الكلمات عن طريق الذكاء الاصطناعي ChatGPT

في هذه الصفحة يمكنك الحصول على تحليل مفصل لكلمة أو عبارة باستخدام أفضل تقنيات الذكاء الاصطناعي المتوفرة اليوم:

  • كيف يتم استخدام الكلمة في اللغة
  • تردد الكلمة
  • ما إذا كانت الكلمة تستخدم في كثير من الأحيان في اللغة المنطوقة أو المكتوبة
  • خيارات الترجمة إلى الروسية أو الإسبانية، على التوالي
  • أمثلة على استخدام الكلمة (عدة عبارات مع الترجمة)
  • أصل الكلمة

%ما هو (من)٪ 1 - تعريف

COMPUTER PROGRAM USED TO TEST AND DEBUG OTHER PROGRAMS
Debuggers; Debugger front end; Debugging tool; Symbolic debugger; Source-level debugger; Debugger (computer); GNU Debugger front end; Omniscient Debugger; User:Unforgettableid/Omniscient Debugger; Debugger front-end; GNU Debugger front-end; Reverse debugging; Reverse debugger; Historical debugger; Historical debugging; Backwards debugger; Backwards debugging; Debugger frontend; Hardware support for debugging
  • [[Winpdb]] debugging itself

source-level debugger         
<programming, tool> 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)
Kernel debugger         
Kernel debugging; Kernel-level debugger
A kernel debugger is a debugger present in some operating system kernels to ease debugging and kernel development by the kernel developers. A kernel debugger might be a stub implementing low-level operations, with a full-blown debugger such as GNU Debugger (gdb), running on another machine, sending commands to the stub over a serial line or a network connection, or it might provide a command line that can be used directly on the machine being debugged.
GDB         
SOURCE-LEVEL DEBUGGER
Gdb; GNU Symbolic Debugger; Gdbtui; Gdb (debugger); GDB; GDB debugger
<programming, tool> GNU debugger. The FSF's {source-level debugger} for C, C++ and other languages. Developed by many people but most recently Fred Fish <fnf@cygnus.com>, Stu Grossman <grossman@cygnus.com> and John Gilmore <gnu@cygnus.com> all of Cygnus Support. GDB fills the same niche as dbx. Programs must be compiled to include debugging symbols. Version 4.11. Distributed under GNU CopyLeft. It runs on most Unix variants, VMS, VXWorks, Amiga and MS-DOS. FTP gdb-*.tar.[zZ] from a GNU archive site. E-mail: <bug-gdb@gnu.org> (bug reports). (1993-10-29)

ويكيبيديا

Debugger

A debugger or debugging tool is a computer program used to test and debug other programs (the "target" program). The main use of a debugger is to run the target program under controlled conditions that permit the programmer to track its execution and monitor changes in computer resources that may indicate malfunctioning code. Typical debugging facilities include the ability to run or halt the target program at specific points, display the contents of memory, CPU registers or storage devices (such as disk drives), and modify memory or register contents in order to enter selected test data that might be a cause of faulty program execution.

The code to be examined might alternatively be running on an instruction set simulator (ISS), a technique that allows great power in its ability to halt when specific conditions are encountered, but which will typically be somewhat slower than executing the code directly on the appropriate (or the same) processor. Some debuggers offer two modes of operation, full or partial simulation, to limit this impact.

A "trap" occurs when the program cannot normally continue because of a programming bug or invalid data. For example, the program might have tried to use an instruction not available on the current version of the CPU or attempted to access unavailable or protected memory. When the program "traps" or reaches a preset condition, the debugger typically shows the location in the original code if it is a source-level debugger or symbolic debugger, commonly now seen in integrated development environments. If it is a low-level debugger or a machine-language debugger it shows the line in the disassembly (unless it also has online access to the original source code and can display the appropriate section of code from the assembly or compilation).