закешированный к нам в целях безопасности дебаггер
Go to file
2014-09-12 15:25:00 -05:00
_fixtures Remove test binaries 2014-09-12 14:56:27 -05:00
_helper Rebuild binaries for every test 2014-09-12 15:19:36 -05:00
command Print context after step, next or continue 2014-09-06 19:39:40 -05:00
dwarf Rebuild binaries for every test 2014-09-12 15:19:36 -05:00
proctl Use consistent fatal test messages 2014-09-06 18:56:25 -05:00
.gitignore Ignore test artifacts 2014-08-04 17:49:36 -05:00
LICENSE Add License and README 2014-05-03 15:31:52 -05:00
main_test.go Recompile test prog for main_test 2014-09-12 15:25:00 -05:00
main.go Launch prog from cli, also exit cleanly 2014-08-23 08:20:56 -05:00
README.md Reword README 2014-09-12 08:13:14 -05:00

DBG

What is DBG?

DBG is a Go debugger, written primarily in Go. It really needs a new name.

Building

Currently, DBG requires the following patch to be applied to your Go source to build.

Features

  • Attach to (trace) a running process
  • Ability to launch a process and begin debugging it
  • Set breakpoints
  • Single step through a process
  • Next through a process (step over / out of subroutines)
  • Never retype commands, empty line defaults to previous command

Usage

The debugger can be launched in two ways:

  • Provide the name of the program you want to debug, and the debugger will launch it for you.

    $ dbg -proc path/to/program
    
  • Provide the pid of a currently running process, and the debugger will attach and begin the session.

    $ sudo dbg -pid 44839
    

Once inside a debugging session, the following commands may be used:

  • break - Set break point at the entry point of a function, or at a specific file/line. Example: break foo.go:13.

  • step - Single step through program.

  • next - Step over to next source line.

Upcoming features

  • Handle Gos multithreaded nature better
  • In-scope variable evaluation
  • In-scope variable setting
  • Readline integration
  • Support for OS X

License

MIT