1. 20 12月, 2016 1 次提交
  2. 06 7月, 2016 1 次提交
  3. 21 6月, 2016 1 次提交
  4. 30 5月, 2016 1 次提交
    • A
      Go 1.7 compatibility (#524) · 9bc6ad4f
      Alessandro Arzilli 提交于
      * tests: update to cope with go1.7 SSA compiler
      
      * de-vendored golang.org/x/debug/dwarf
      
      We need our own tweaked version
      
      * dwarf/debug/dwarf: always use the entry's name attribute
      
      Using the name attribute leads to better type names as well as fixes
      inconsistencies between 1.5, 1.6 and 1.7.
      
      * proc: Updated loadInterface to work with go1.7
      
      go1.7 changed the internal representation of types, removing the string
      field from runtime._type.
      Updated loadInterface to use the new str field.
      9bc6ad4f
  5. 25 4月, 2016 1 次提交
    • A
      proc: Improvements to Variable printing (#444) · 473b6638
      Alessandro Arzilli 提交于
      * service/api: Removed unused fields of service/api.Function
      
      * proc/eval: Set return variable name to input expression
      
      * all: fine-grained control of loadValue for better variable printing
      
      Makes proc.(*Variable).loadValue loading parameters configurable
      through one extra argument of type LoadConfig.
      This interface is also exposed through the API so clients can control
      how much of a variable delve should read.
      473b6638
  6. 17 2月, 2016 1 次提交
  7. 12 2月, 2016 1 次提交
  8. 25 1月, 2016 1 次提交
    • A
      proc: replace debug/dwarf with golang.org/x/debug/dwarf · 54f1c9b3
      aarzilli 提交于
      Typedefs that resolve to slices are not recorded in DWARF as typedefs
      but instead as structs in a way that there is no way to know they
      are really slices using debug/dwarf.
      Using golang.org/x/debug/dwarf instead this problem is solved and
      as a bonus some types are printed with a nicer names: (struct string
      → string, struct []int → []int, etc)
      
       Fixes #356 and #293
      54f1c9b3
  9. 10 1月, 2016 1 次提交
  10. 09 1月, 2016 2 次提交
    • A
      proc: Next implemented as conditional breakpoints + Continue · 54411356
      aarzilli 提交于
      Next sets its temporary breakpoints with the condition that they
      must only activate on the current goroutine, and then calls Continue
      When Continue encounters a temporary breakpoint it clears all
      the breakpoint.
      
      User visible changes: breakpoints that get hit while executing Next
      are not ignored.
      
      This commit does not implement full conditional breakpoints
      functionality, the only condition that can be set is on the
      goroutine id.
      
      Fixes race conditions in Next affecting TestNextConcurrent.
      54411356
    • A
      service,terminal: propagating simultaneous breakpoints · 708cf2f2
      aarzilli 提交于
      708cf2f2
  11. 16 12月, 2015 1 次提交
  12. 04 11月, 2015 1 次提交
    • A
      proc: Implements expression interpreter · 43b64ec3
      aarzilli 提交于
      Supported operators:
      
      - All (binary and unary) operators between basic types except <-,
      ++ and -- (includes & to take the address of an expression)
      - Comparison operators between supported compound types
      - Typecast of integer constants into pointer types
      - struct members
      - indexing of arrays, slices and strings
      - slicing of arrays, slices and strings
      - pointer dereferencing
      - true, false and nil constants
      
      Implements #116, #117 and #251
      43b64ec3
  13. 29 10月, 2015 3 次提交
  14. 19 10月, 2015 2 次提交
  15. 10 10月, 2015 1 次提交
  16. 20 8月, 2015 1 次提交
  17. 13 7月, 2015 1 次提交
    • D
      Implement 'trace' subcommand · 3cee10d8
      Derek Parker 提交于
      Allows a user to execute `dlv trace [regexp]` and Delve will execute the
      program and output information on functions matching [regexp].
      3cee10d8
  18. 01 7月, 2015 1 次提交
    • D
      Cleanup tracepoint commit · 6b99c5f5
      Derek Parker 提交于
      * Cleanup comments
      * Cleanup naming in certain instances
      * Modify stacktrace to return current location
      6b99c5f5
  19. 30 6月, 2015 1 次提交
  20. 21 6月, 2015 1 次提交
  21. 14 6月, 2015 1 次提交
    • D
      Refactor: Use thread-locked goroutine for ptrace ops · e4fc5e32
      Derek Parker 提交于
      Previously either the terminal client or the debugger service would
      either lock main goroutine to a thread or provide a locked goroutine to
      run _all_ DebuggedProcess functions in. This is unnecessary because only
      ptrace functions need to be run from the same thread that originated the
      PT_ATTACH request.
      
      Here we use a specific thread-locked goroutine to service any ptrace
      request. That goroutine is also responsible for the initial spawning /
      attaching of the process, since it must be responsible for the PT_ATTACH
      request.
      e4fc5e32