Types of debuggers
Types of debuggers
• 1. Kernel debugger:
• 2. Basic machine-level debugger
• 3. In-circuit emulator:
• 4. Interpretive programming environment
debugger:
1. Kernel debugger:
• o It is for dealing with problems with an OS kernel
on its own or for interactions between OS-
dependent applications and the OS
• o A kernel debugger might be a stub
implementing low-level operations, with a full
blown debugger such as 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.
• o The Windows NT family includes a kernel
debugger named KD, which can act as a local
debugger with limited capabilities
2. Basic machine-level debugger
• o It is used for debugging the actual running code as
they are processed by the CPU
• o The debugger lets you debug your programs at the
machine-code level as well as at the source-code
level. Using debugger commands, you can examine
and edit values in memory, print the values of all
machine registers, and step through program
execution one machine instruction at a time.
• o Only those users familiar with machine-language
programming and executable-filecode structure will
find low-level debugging useful.
• o ( Examining memory addresses, stepping at the
machine level, disassembling etc)
3. In-circuit emulator:
• o It emulates the system services so that all
interactions between an application and the system
can be monitored and traced. It sit between the OS
and the bare hardware. It watch and monitor all
processes and all interactions between applications
and OS.
• o In-circuit emulation (ICE) is the use of a hardware
device or in-circuit emulator used to debug the
software of an embedded system. It operates by
using a processor with the additional ability to
support debugging operations, as well as to carry
out the main function of the system.
4. Interpretive programming
environment debugger:
• o Debugger is integrated into the runtime interpreter and
has tight control over the running application
• o In computer science, an interpreter is a computer
program that directly executes, i.e. performs, instructions
written in a programming or scripting language, without
requiring them previously to have been compiled into a
machine language program.
• o An interpreter generally uses one of the following
strategies for program execution:
– Parse the source code and perform its behavior directly;
– Translate source code into some efficient intermediate
representation and immediately execute this;
– Explicitly execute stored precompiled code made by a
compiler which is part of the interpreter system
• Almost high-level languages have interpreters which are
usually used at the time of development process with
the aim of error correction.
BUG TRACKING
BUG TRACKING
• A bug tracking system is a software
application that is designed to help quality
assurance and programmers keep track of
reported software bugs in software
development projects.
• • A major component of bug tracking
system is a database that records facts
and known bugs
Defect Tracking Parameters
• Defect Tracking Parameters
• • Defects are tracked based on various
parameters such as:
• • Defect Id, Priority, Severity, Created by,
Created Date, Assigned to, Resolved Date,
Resolved By, Status
Methods of Bug Tracking
Administrator
• He can record the team, staff and project
entry.
• If he finds that the process of project is
not done on time, then he can assign that
project to another team.
• • He can keep record of the status of all
the projects along with the bug details.
Developer
• • When he logins , he can see all the bug
details assigned to him.
• • Details of the project that bug belongs to.
• • Can see the members of the team.
• • Can change the status of the bug.
• • Can report the process of the bug to the
tester
• • Can see the status of the project assigned
to him
Tester
• • When he logins, he can see the details of
the project that are assigned to him.
• • He can get an interface for defect bug.
• • He can see the members of the team.
• • He should have the right to see or
change the status of the project.
• • He can see or change the status of the
bug.
Analyst
• • He can generate various reports.
• • He can allot the bug to the developer of his team.
• • If he does not find work on time, then he will allot the bug to
another developer of his team.
• • He can see the members of his team.
• • Admin will allot the staff and then forms a team.
• • Admin will assign the roles to developer, analyst and tester.
• • The team will be assigned the project to deal with.
• • Tester will report the bugs and the status of the bug will be
recorded.
• • That bug will be then forwarded to the analyst .
• • Analyst will allot that bug to the developer.
• • Developer can see all the bug details assigned to him.
• • Can change the status of the bug.
• • Can report the process of the bug to the tester
