- 20 2月, 2020 1 次提交
-
-
由 chainhelen 提交于
Avoid panic if start addr is greater than end addr when disasm.
-
- 19 2月, 2020 1 次提交
-
-
由 Sylvain Rabot 提交于
Signed-off-by: NSylvain Rabot <s.rabot@lectra.com>
-
- 18 2月, 2020 2 次提交
-
-
由 ossdev07 提交于
* proc/native: optimize native.status through buffering (#1865) Benchmark before: BenchmarkConditionalBreakpoints-4 1 15649407130 ns/op Benchmark after: BenchmarkConditionalBreakpoints-4 1 14586710018 ns/op Conditional breakpoint evaluation 1.56ms -> 1.45ms Updates #1549 * proc/core: Review Comments Incorporated Signed-off-by: Nossdev07 <ossdev@puresoftware.com> Co-authored-by: NAlessandro Arzilli <alessandro.arzilli@gmail.com>
-
由 Alessandro Arzilli 提交于
runtime.g is a large and growing struct, we only need a few fields. Instead of using loadValue to load the full contents of g, cache its memory and then only load the fields we care about. Benchmark before: BenchmarkConditionalBreakpoints-4 1 14586710018 ns/op Benchmark after: BenchmarkConditionalBreakpoints-4 1 12476166303 ns/op Conditional breakpoint evaluation: 1.45ms -> 1.24ms Updates #1549
-
- 16 2月, 2020 2 次提交
-
-
由 Alessandro Arzilli 提交于
Benchmark before: BenchmarkConditionalBreakpoints-4 1 15649407130 ns/op Benchmark after: BenchmarkConditionalBreakpoints-4 1 14586710018 ns/op Conditional breakpoint evaluation 1.56ms -> 1.45ms Updates #1549
-
由 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
-
- 15 2月, 2020 1 次提交
-
-
由 Alessandro Arzilli 提交于
Logged errors should be visible even if the corresponding flag was not selected.
-
- 14 2月, 2020 3 次提交
-
-
由 Derek Parker 提交于
Instead of reloading the registers for every thread every time the process executes, reload the registers on demand for individual threads and memoize the result.
-
由 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.
-
由 Alessandro Arzilli 提交于
The stacktrace code occasionally needs the value of g.m.g0.sched.sp to switch stacks. Since this is only needed rarely and calling parseG is relatively expensive we should delay doing it until we know it will be needed. Benchmark before: BenchmarkConditionalBreakpoints-4 1 17326345671 ns/op Benchmark after: BenchmarkConditionalBreakpoints-4 1 15649407130 ns/op Reduces conditional breakpoint latency from 1.7ms to 1.56ms. Updates #1549
-
- 13 2月, 2020 3 次提交
-
-
由 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
-
由 vpsx 提交于
Changes docs to reflect different possible locations for config/history files.
-
由 Kirides 提交于
I think that should've been 2020 ;)
-
- 12 2月, 2020 1 次提交
-
-
由 Alessandro Arzilli 提交于
* service: also search IPv6 connections when checking user When checking if the user is allowed to connect to this Delve instance also search IPv6 connections even though the local address is IPv4. Fixes #1835 * cmd: add flag to disable same-user check Fixes #1835
-
- 11 2月, 2020 3 次提交
-
-
由 aarzilli 提交于
Thank you to: @stapelberg, @hengwu0, @tykcd996, @chainhelen, @alexbrainman, @nd and @stigok.
-
由 chainhelen 提交于
-
由 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
-
- 29 1月, 2020 2 次提交
-
-
由 Stig Otnes Kolstad 提交于
-
由 chainhelen 提交于
-
- 28 1月, 2020 3 次提交
-
-
由 aarzilli 提交于
It was reading all the way to the end of the debug_info section, slowing down stacktraces substantially. Benchmark before: BenchmarkConditionalBreakpoints-4 1 80344642562 ns/op Benchmark after: BenchmarkConditionalBreakpoints-4 1 22218288218 ns/op i.e. a reduction of the cost of a breakpoint hit from 8ms to 2.2ms Updates #1549
-
由 aarzilli 提交于
-
由 aarzilli 提交于
It is not used anymore besides internally by the proc/gdbserial backend.
-
- 27 1月, 2020 1 次提交
-
-
由 chainhelen 提交于
-
- 23 1月, 2020 1 次提交
-
-
由 chainhelen 提交于
-
- 22 1月, 2020 6 次提交
-
-
由 Derek Parker 提交于
It seems the project in AppVeyor moved from go-delve to my AppVeyor account and I'm not sure how that happened. However, it did break the badge rendering on the README so this patch fixes it with the current correct link.
-
由 Derek Parker 提交于
* pkg/proc: Introduce Target * pkg/proc: Remove Common.fncallEnabled Realistically we only block it on recorded backends. * pkg/proc: Move fncallForG to Target * pkg/proc: Remove CommonProcess Remove final bit of functionality stored in CommonProcess and move it to *Target. * pkg/proc: Add SupportsFunctionCall to Target
-
由 hengwu0 提交于
* proc: separate amd64-arch code separate amd64 code about stacktrace, so we can add arm64 stacktrace code. * proc: implemente stacktrace of arm64 * delve now can use stack, frame commands on arm64-arch debug. Co-authored-by: Ntykcd996 <tang.yuke@zte.com.cn> Co-authored-by: Nhengwu0 <wu.heng@zte.com.cn> * test: remove skip-code of stacktrace on arm64 * add LR DWARF register and remove skip-code for fixed tests * proc: fix the Continue command after the hardcoded breakpoint on arm64 Arm64 use hardware breakpoint, and it will not set PC to the next instruction like amd64. We should move PC in both runtime.breakpoints and hardcoded breakpoints(probably cgo). * proc: implement cgo stacktrace on arm64 * proc: combine amd64_stack.go and arm64_stack.go file * proc: reorganize the stacktrace code * move SwitchStack function arch-related * fix Continue command after manual stop on arm64 * add timeout flag to make.go to enable infinite timeouts Co-authored-by: Naarzilli <alessandro.arzilli@gmail.com> Co-authored-by: Nhengwu0 <wu.heng@zte.com.cn> Co-authored-by: Ntykcd996 <56993522+tykcd996@users.noreply.github.com> Co-authored-by: NAlessandro Arzilli <alessandro.arzilli@gmail.com>
-
由 Dmitry Neverov 提交于
-
由 Dmitry Neverov 提交于
Labels can help in identifying a particular goroutine during debugging. Fixes #1763
-
由 chainhelen 提交于
Abandon gitter chat link, just leave the mailing list. Fix #1842
-
- 21 1月, 2020 1 次提交
-
-
由 chainhelen 提交于
Expression such as: config show-location-expr true disassemble -a 0x4a23a0 0x4a23f2 disassemble -a 0x4a23a0 0x4a23f2 should all execute correctly. Extend #795.
-
- 17 1月, 2020 1 次提交
-
-
由 aarzilli 提交于
Adds a cache mapping goroutine IDs to goroutine objects, this allows speeding up FindGoroutine and makes commands like 'goroutines -t' not be accidentally quadratic in the number of goroutines.
-
- 14 1月, 2020 3 次提交
-
-
由 chainhelen 提交于
Should judge `state.Err` instead of `err`.
-
由 Derek Parker 提交于
We've dropped support for 1.11 in our CI runs, we should also update the minimum require Go version in the mod file as well. Resolves #1813
-
由 Alex Brainman 提交于
Specifically, make sure that both DebugActiveProcess and WaitForDebugEvent Windows APIs are executed on the same thread. Otherwise WaitForDebugEvent fails with ERROR_INVALID_HANDLE as per its documentation https://docs.microsoft.com/en-us/windows/win32/api/debugapi/nf-debugapi-waitfordebugevent '... Only the thread that created the process being debugged can call WaitForDebugEvent. ...' Fixes #1825
-
- 10 1月, 2020 4 次提交
-
-
由 aarzilli 提交于
Due to a bug in the Go compiler midstack inlined calls do not report their ranges correctly. We can't check if an address is in the range of a DIE by simply looking at that DIE's range, we should also recursively check the DIE's children's ranges. Also fixes the way stacktraces of midstack inlined calls are reported (they used to be inverted, with the deepest inlined stack frame reported last). Fixes #1795
-
由 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.
-
由 aarzilli 提交于
When a line has instructions associated but none of them have is_stmt set LineToPC and LineToPCIn should behave in the same way. Fixes #1817
-
由 chainhelen 提交于
Change `copy form` into `copy from`.
-
- 03 1月, 2020 1 次提交
-
-
由 aarzilli 提交于
-