Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 47 views

    Testing and Debugging: Jithin Jacob Lecturer Dept of CSE, MACE

    Uploaded by

    Jeena Mol Abraham
    This document discusses testing and debugging programs. It provides an overview of testing, which involves running programs to find bugs, and debugging, which involves finding and fixing errors. It then discusses various debugging techniques in GNU Debugger (GDB) like setting breakpoints, stepping through code, and examining backtraces. These techniques allow debugging programs line-by-line to locate bugs. The document also covers debugging crashed programs using core dumps.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd

    Testing and Debugging: Jithin Jacob Lecturer Dept of CSE, MACE

    Uploaded by

    Jeena Mol Abraham
    47 views14 pages
    This document discusses testing and debugging programs. It provides an overview of testing, which involves running programs to find bugs, and debugging, which involves finding and fixing errors. It then discusses various debugging techniques in GNU Debugger (GDB) like setting breakpoints, stepping through code, and examining backtraces. These techniques allow debugging programs line-by-line to locate bugs. The document also covers debugging crashed programs using core dumps.

    Original Description:

    assemblers

    Original Title

    Testing and Debugging

    Copyright

    © © All Rights Reserved

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses testing and debugging programs. It provides an overview of testing, which involves running programs to find bugs, and debugging, which involves finding and fixing errors. It then discusses various debugging techniques in GNU Debugger (GDB) like setting breakpoints, stepping through code, and examining backtraces. These techniques allow debugging programs line-by-line to locate bugs. The document also covers debugging crashed programs using core dumps.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    47 views14 pages

    Testing and Debugging: Jithin Jacob Lecturer Dept of CSE, MACE

    Uploaded by

    Jeena Mol Abraham
    This document discusses testing and debugging programs. It provides an overview of testing, which involves running programs to find bugs, and debugging, which involves finding and fixing errors. It then discusses various debugging techniques in GNU Debugger (GDB) like setting breakpoints, stepping through code, and examining backtraces. These techniques allow debugging programs line-by-line to locate bugs. The document also covers debugging crashed programs using core dumps.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    of 14

    Testing and Debugging

    JITHIN JACOB
    Lecturer
    Dept of CSE , MACE
    Debugging and testing
    Testing: running a program with
    the intent of finding bugs
    Debugging: once errors are
    found,finding the exact nature of a
    suspected programming error and
    fixing it
    95% of the time of
    debugging is finding the
    syntactic bugs
    cause of
    design bugs
    a problem
    logic bugs
    interface bugs
    memory bugs
    WHATS GNU??
    GNU IS NOT UNIX

    WHY A NAME LIKE THAT ??


    The GNU debugger (gdb)
    GDB is a debugger that helps you to
    debug your program.
    Compiling a program for
    gdb
    You need to compile with the -g
    option to be able to debug a
    program with gdb.
    The -g option adds debugging
    information to your program
    gcc g hello.c
    Running a Program with
    gdb
    To run a program with gdb type
    gdb progname
    (gdb)
    Then set a breakpoint in the main function.
    (gdb) break main
    A breakpoint is a marker in your program that will make
    the program stop and return control back to gdb.
    Now run your program.
    (gdb) run
    If your program has arguments, you can pass them after
    run.
    Stepping Through your
    Program
    Your program will start running and when it
    reaches main() it will stop.
    gdb>
    Now you have the following commands to run
    your program step by step:
    (gdb) step
    It will run the next line of code and stop. If it is a function
    call, it will enter into it
    (gdb) next
    It will run the next line of code and stop. If it is a function
    call, it will not enter the function and it will go through it.
    Example:
    (gdb) step
    (gdb) next
    Setting breakpoints
    You can set breakpoints in a program in multiple
    ways:
    (gdb) break function
    Set a breakpoint in a function E.g.
    (gdb) break main
    (gdb) break line
    Set a break point at a line in the current file. E.g.
    (gdb) break 66
    It will set a break point in line 66 of the current file.
    (gdb) break file:line
    It will set a break point at a line in a specific file. E.g.
    (gdb) break hello.c:78
    Where is your Program
    The command
    (gdb)where
    Will print the current function being executed
    and the chain of functions that are calling
    that function.
    This is also called the backtrace
    Exiting gdb
    The command quit exits gdb.
    (gdb) quit
    The program is running. Exit
    anyway? (y or n) y
    Debugging a Crashed
    Program
    This is also called postmortem debugging

    When a program crashes, it writes a core file.


    bash-4.1$ ./hello
    Segmentation Fault (core dumped)
    bash-4.1$

    The core is a file that contains a snapshot of


    the program at the time of the crash. That
    includes what function the program was
    running.
    Execution commands
    run or r (run program from beginning)
    start
    starts debugging, breaks at main
    kill
    stops debugging
    More Execution commands
    next or n
    execute next line, stepping over
    function calls
    step or s
    execute next line, stepping into
    function calls
    continue or cont
    resume execution, until next breakpoint

    You might also like