1. 22 2月, 2020 1 次提交
  2. 20 2月, 2020 2 次提交
  3. 16 2月, 2020 1 次提交
    • P
      service/dap: Initial implementation for 'dlv dap' (#1858) · fbc4623c
      polinasok 提交于
      * Initial implementation for 'dlv dap'
      
      * Fix Travis and AppVeyor failures
      
      * Address review comments
      
      * Address review comments
      
      * Regenrate documentation
      
      * Replace dap server printfs with log.Error
      
      * Update 'dap log'
      
      * Fix typos
      
      * Revert logflags changes that got mixed in by accident
      fbc4623c
  4. 14 2月, 2020 1 次提交
    • C
      pkg,service: add cmd `examinemem`(`x`) for examining memory. (#1814) · a5d9dbee
      chainhelen 提交于
      According to #1800 #1584 #1038, `dlv` should enable the user to dive into
      memory. User can print binary data in specific memory address range.
      But not support for sepecific variable name or structures temporarily.(Because
      I have no idea that modify `print` command.)
      
      Close #1584.
      a5d9dbee
  5. 13 2月, 2020 1 次提交
    • A
      proc: only format registers value when it's necessary (#1860) · b9d0ddd8
      Alessandro Arzilli 提交于
      A significant amount of time is spent generating the string
      representation for the proc.Registers object of each thread, since this
      field is rarely used (only when the Registers API is called) it should
      be generated on demand.
      
      Also by changing the internal representation of proc.Register to be
      closer to that of op.DwarfRegister it will help us implement #1838
      (when Delve will need to be able to display the registers of an
      internal frame, which we currently represent using op.DwarfRegister
      objects).
      
      Benchmark before:
      
      BenchmarkConditionalBreakpoints-4   	       1	22292554301 ns/op
      
      Benchmark after:
      
      BenchmarkConditionalBreakpoints-4   	       1	17326345671 ns/op
      
      Reduces conditional breakpoint latency from 2.2ms to 1.7ms.
      
      Updates #1549, #1838
      b9d0ddd8
  6. 12 2月, 2020 1 次提交
  7. 11 2月, 2020 1 次提交
    • A
      *: Go 1.14 support branch (#1727) · 0741d3e5
      Alessandro Arzilli 提交于
      * tests: misc test fixes for go1.14
      
      - math.go is now ambiguous due to changes to the go runtime so specify
        that we mean our own math.go in _fixtures
      - go list -m requires vendor-mode to be disabled so pass '-mod=' to it
        in case user has GOFLAGS=-mod=vendor
      - update version of go/packages, required to work with go 1.14 (and
        executed go mod vendor)
      - Increased goroutine migration in one development version of Go 1.14
        revealed a problem with TestCheckpoints in command_test.go and
        rr_test.go. The tests were always wrong because Restart(checkpoint)
        doesn't change the current thread but we can't assume that when the
        checkpoint was taken the current goroutine was running on the same
        thread.
      
      * goversion: update maximum supported version
      
      * Makefile: disable testing lldb-server backend on linux with Go 1.14
      
      There seems to be some incompatibility with lldb-server version 6.0.0
      on linux and Go 1.14.
      
      * proc/gdbserial: better handling of signals
      
      - if multiple signals are received simultaneously propagate all of them to the
        target threads instead of only one.
      - debugserver will drop an interrupt request if a target thread simultaneously
        receives a signal, handle this situation.
      
      * dwarf/line: normalize backslashes for windows executables
      
      Starting with Go 1.14 the compiler sometimes emits backslashes as well
      as forward slashes in debug_line, normalize everything to / for
      conformity with the behavior of previous versions.
      
      * proc/native: partial support for Windows async preempt mechanism
      
      See https://github.com/golang/go/issues/36494 for a description of why
      full support for 1.14 under windows is problematic.
      
      * proc/native: disable Go 1.14 async preemption on Windows
      
      See https://github.com/golang/go/issues/36494
      0741d3e5
  8. 22 1月, 2020 4 次提交
  9. 14 1月, 2020 1 次提交
  10. 10 1月, 2020 1 次提交
    • A
      proc,service: return build informations for each package · a8606afb
      aarzilli 提交于
      Adds an API call that returns a list of packages contained in the
      program and the files that were used to build them, and also a best
      guess at which filesystem directory contained the package when it was
      built.
      
      This can be used by IDEs to map file paths if the debugging environment
      doesn't match the build environment exactly.
      a8606afb
  11. 03 1月, 2020 1 次提交
  12. 10 12月, 2019 1 次提交
  13. 28 11月, 2019 4 次提交
  14. 26 11月, 2019 2 次提交
  15. 05 11月, 2019 1 次提交
  16. 02 11月, 2019 1 次提交
    • A
      proc,debugger: implement logical breakpoints (#1717) · 222deeec
      Alessandro Arzilli 提交于
      Modifies FindFileLocation, FindFunctionLocation and LineToPC as well as
      service/debugger to support inlining and introduces the concept of
      logical breakpoints.
      
      For inlined functions FindFileLocation, FindFunctionLocation and
      LineToPC will now return one PC address for each inlining and one PC
      for the concrete implementation of the function (if present).
      
      A proc.Breakpoint will continue to represent a physical breakpoint, at
      a single memory location.
      
      Breakpoints returned by service/debugger, however, will represent
      logical breakpoints and may be associated with multiple memory
      locations and, therefore, multiple proc.Breakpoints.
      
      The necessary logic is introduced in service/debugger so that a change
      to a logical breakpoint will be mirrored to all its physical
      breakpoints and physical breakpoints are aggregated into a single
      logical breakpoint when returned.
      222deeec
  17. 29 10月, 2019 1 次提交
    • A
      proc: always resolve array types even if they don't appear in the · 5a947bce
      aarzilli 提交于
      program
      
      When evaluating type casts always resolve array types.
      
      Instead of resolving them by looking up the string in debug_info
      construct a fake array type so that a type cast to an array type always
      works as long as the element type exists.
      
      We already did this for byte arrays, this commit extends this to any
      array type. The reason is that we return a fake array type (that
      doesn't exist in the target program) for the array of a channel type.
      
      Fixes #1736
      5a947bce
  18. 26 10月, 2019 1 次提交
  19. 23 10月, 2019 1 次提交
  20. 22 10月, 2019 1 次提交
  21. 08 10月, 2019 2 次提交
  22. 26 9月, 2019 3 次提交
  23. 14 8月, 2019 1 次提交
  24. 10 8月, 2019 1 次提交
  25. 30 7月, 2019 1 次提交
    • D
      *: Add .cirrus.yml for FreeBSD testing (#1639) · f4eaad69
      Derek Parker 提交于
      * *: Add .cirrus.yml for FreeBSD testing
      
      * *: run go mod tidy
      
      * service/test: prefer 127.0.0.1 over localhost
      
      * dwarf/line: fix TestDebugLinePrologueParser
      
      * vendor: rerun go mod vendor
      f4eaad69
  26. 28 7月, 2019 1 次提交
  27. 17 7月, 2019 1 次提交
  28. 13 7月, 2019 1 次提交
    • R
      *: FreeBSD initial support (#1480) · df65be43
      Robert Ayrapetyan 提交于
      * FreeBSD initial support
      
      * first code review fixes
      
      * regs slice upd
      
      * execPtraceFunc wrap
      
      * disabled concurrency tests
      fixed kill() issue
      
      * disabled concurrency tests
      fixed kill() issue
      
      * cleanup vendor related code
      
      * cleanup ptrace calls
      
      * vendoring latest changes
      
      * Revert "vendoring latest changes"
      
      This reverts commit 833cb87b
      
      * vendoring latest changes
      
      * requested changes
      df65be43
  29. 09 7月, 2019 1 次提交