zoukankan      html  css  js  c++  java
  • GDB 主要调试命令

    GDB(1) GNU Development Tools GDB(1)

    NAME
    gdb - The GNU Debugger

    SYNOPSIS
    gdb [-help] [-nh] [-nx] [-q] [-batch] [-cd=dir] [-f] [-b bps]
    [-tty=dev] [-s symfile] [-e prog] [-se prog] [-c core] [-p procID]
    [-x cmds] [-d dir] [prog|prog procID|prog core]

    DESCRIPTION
    The purpose of a debugger such as GDB is to allow you to see what is going on “inside” another program while it executes – or what another program was doing at the moment it crashed.

       GDB can do four main kinds of things (plus other things in support of 
       these) to help you catch bugs in the act:
    
       ·   Start your program, specifying anything that might affect its
        behavior.
    
       ·   Make your program stop on specified conditions.
    
       ·   Examine what has happened, when your program has stopped.
    
       ·   Change things in your program, so you can experiment with
       correcting the effects of one bug and go on to learn about another.
    
       You can use GDB to debug programs written in C, C@t{++}, Fortran and
        Modula-2.
    
       GDB is invoked with the shell command "gdb".  Once started, it reads 
       commands from the terminal until you tell it to exit with the GDB
       command "quit".  You can get online help from GDB itself by using the
       command "help".
    
       You can run "gdb" with no arguments or options; but the most usual way
       to start GDB is with one argument or two, specifying an executable
       program as the argument:
    
               gdb program
    
       You can also start with both an executable program and a core file
       specified:
    
               gdb program core
    
       You can, instead, specify a process ID as a second argument, if you
       want to debug a running process:
    
               gdb program 1234
               gdb -p 1234
    
       would attach GDB to process 1234 (unless you also have a file named
       1234; GDB does check for a core file first).  With option -p you can
       omit the program filename.
    

    Here are some of the most frequently needed GDB commands:

       break [file:]functiop
           Set a breakpoint at function (in file).
    
       run [arglist]
           Start your program (with arglist, if specified).
    
       bt  Backtrace: display the program stack.
    
       print expr
           Display the value of an expression.
    
       c   Continue running your program (after stopping, e.g. at a breakpoint).
    
       next
           Execute next program line (after stopping); step over any function
           calls in the line.
    
       edit [file:]function
           look at the program line where it is presently stopped.
    
       list [file:]function
           type the text of the program in the vicinity of where it is
           presently stopped.
    
       step
           Execute next program line (after stopping); step into any function
           calls in the line.
    
       help [name]
           Show information about GDB command name, or general information
            about using GDB.
    
       quit
           Exit from GDB.
    
       For full details on GDB, see Using GDB: A Guide to the GNU Source-Level
       available online  as the "gdb" entry in the "info" program.
    
  • 相关阅读:
    atitit.解决net.sf.json.JSONException There is a cycle in the hierarchy
    atitit.查看预编译sql问号 本质and原理and查看原生sql语句
    atitit.基于http json api 接口设计 最佳实践 总结o7
    atitit.spring3 mvc url配置最佳实践
    Atitit.列表页面and条件查询的实现最佳实践(2)翻页 分页 控件的实现java .net php
    atitit。自定义uml MOF EMF体系eclipse emf 教程o7t
    atitit.编辑表单的实现最佳实践dwr jq easyui
    Atitit. 提升开发效率与质量DSL ( 3) 实现DSL的方式总结
    atitit.设计模式(2) 查表模式/ command 总结
    Atitit. 提升软件开发效率and 开发质量java 实现dsl 4gl 的本质and 精髓 O725
  • 原文地址:https://www.cnblogs.com/brother-louie/p/13976553.html
Copyright © 2011-2022 走看看