Switch to Bing in English
About 4,400,000 results
Open links in new tab
  1. GNU gdb how to show source file name and lines of a symbol

    Dec 25, 2013 · 19 when use GNU gdb to debug a c process. list command will print the lines but not telling me the file name. set breakpoints can display all the line and file info I want but I don't want to …

  2. Files (Debugging with GDB) - sourceware.org

    file filename Use filename as the program to be debugged. It is read for its symbols and for the contents of pure memory. It is also the program executed when you use the run command. If you do not …

  3. list list <filename>:<function> list <filename>:<line_number> list <first>,<last> Shows the current or given source con-text. The filename may be omitted. If last is omitted the context starting at start is printed …

  4. Debugging with GDB - Examining Source Files

    Specifies the line of the open-brace that begins the body of the function function in the file filename. You only need the file name with a function name to avoid ambiguity when there are identically named …

  5. Debugging with GDB - GDB Files - GNU

    All file-specifying commands allow both absolute and relative file names as arguments. GDB always converts the file name to an absolute file name and remembers it that way.

  6. Debugging with GDB: GDB Files - Florida State University

    You can change the value of this variable, for both GDB and your program, using the path command. On systems with memory-mapped files, an auxiliary file named `filename.syms' may hold symbol table …

  7. List (Debugging with GDB) - sourceware.org

    List (Debugging with GDB)Repeating a list command with RET discards the argument, so it is equivalent to typing just list. This is more useful than listing the same lines again. An exception is made for an …

  8. GDB: How to list all source files used for compilation

    Apr 2, 2014 · In DDD (gui based gdb), there is a Menu: File->List, which lists all the source files used and static libraries used for building the executable. Unfortunately, for command line based debugger …