- 24 7月, 2019 1 次提交
-
-
由 Michail Safronov 提交于
* add max-variable-recurse parameter
-
- 18 7月, 2019 1 次提交
-
-
由 Brian de Alwis 提交于
-
- 13 7月, 2019 2 次提交
-
-
由 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
-
由 qingyunha 提交于
-
- 09 7月, 2019 3 次提交
-
-
由 Derek Parker 提交于
-
由 dpapastamos 提交于
Support for rev {next,step} is not currently implemented.
-
由 Alessandro Arzilli 提交于
Fixes #1598
-
- 03 7月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
If the argument of 'source' ends in '.star' it will be interpreted as a starlark script. If the argument of 'source' is '-' an interactive starlark repl will be started. For documentation on how the starlark execution environment works see Documentation/cli/starlark.md. The starlark API is autogenerated from the JSON-RPC API by script/gen-starlark-bindings.go. In general for each JSON-RPC API a single global starlark function is created. When one of those functions is called (through a starlark script) the arguments are converted to go structs using reflection. See unmarshalStarlarkValue in pkg/terminal/starbind/conv.go. If there are no type conversion errors the JSON-RPC call is executed. The return value of the JSON-RPC call is converted back into a starlark value by interfaceToStarlarkValue (same file): * primitive types (such as integers, floats or strings) are converted by creating the corresponding starlark value. * compound types (such as structs and slices) are converted by wrapping their reflect.Value object into a type that implements the relevant starlark interfaces. * api.Variables are treated specially so that their Value field can be of the proper type instead of always being a string. Implements #1415, #1443
-
- 02 7月, 2019 1 次提交
-
-
由 dpapastamos 提交于
-
- 01 7月, 2019 2 次提交
-
-
由 Alessandro Arzilli 提交于
* proc: allow simultaneous call injection to multiple goroutines Changes the call injection code so that we can have multiple call injections going on at the same time as long as they happen on distinct goroutines. * proc: fix EvalExpressionWithCalls for constant expressions The lack of address of constant expressions would confuse EvalExpressionWithCalls Fixes #1577
-
由 Alessandro Arzilli 提交于
* tests: fix tests for Go 1.13 - Go 1.13 doesn't autogenerate init functions anymore, tests that expected that now fail and should be skipped. - Plugin tests now need -gcflags'all=-N -l' now, we were probably getting lucky with -gcflags='-N -l' before. * proc: allow signed integers as shift counts Go1.13 allows signed integers to be used as the right hand side of a shift operator, change eval to match. * goversion: update maximum supported version * travis: force Go to use vendor directory Travis scripts get confused by "go: downloading" lines, the exact reason is not clear. Testing that the vendor directory is up to date is a good idea anyway.
-
- 31 5月, 2019 1 次提交
-
-
由 Sean Chen 提交于
-
- 09 5月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
This change splits the BinaryInfo object into a slice of Image objects containing information about the base executable and each loaded shared library (note: go plugins are shared libraries). Delve backens are supposed to call BinaryInfo.AddImage whenever they detect that a new shared library has been loaded. Member fields of BinaryInfo that are used to speed up access to dwarf (Functions, packageVars, consts, etc...) remain part of BinaryInfo and are updated to reference the correct image object. This simplifies this change. This approach has a few shortcomings: 1. Multiple shared libraries can define functions or globals with the same name and we have no way to disambiguate between them. 2. We don't have a way to handle library unloading. Both of those affect C shared libraries much more than they affect go plugins. Go plugins can't be unloaded at all and a lot of name collisions are prevented by import paths. There's only one problem that is concerning: if two plugins both import the same package they will end up with multiple definition for the same function. For example if two plugins use fmt.Printf the final in-memory image (and therefore our BinaryInfo object) will end up with two copies of fmt.Printf at different memory addresses. If a user types break fmt.Printf a breakpoint should be created at *both* locations. Allowing this is a relatively complex change that should be done in a different PR than this. For this reason I consider this approach an acceptable and sustainable stopgap. Updates #865
-
- 28 3月, 2019 1 次提交
-
-
由 aarzilli 提交于
Add options to the stack command to read the goroutine ancestors. Ancestor tracking was added to Go 1.12 with CL: https://go-review.googlesource.com/c/go/+/70993/ Implements #1491
-
- 21 3月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
Adds initial support for plugins, this is only the code needed to keep track of loaded plugins on linux (both native and gdbserial backend). It does not actually implement support for debugging plugins on linux. Updates #865
-
- 27 2月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
Fixes #1493
-
- 05 1月, 2019 2 次提交
-
-
由 Derek Parker 提交于
The repository is being switched from the personal account github.com/derekparker/delve to the organization account github.com/go-delve/delve. This patch updates imports and docs, while preserving things which should not be changed such as my name in the CHANGELOG and in TODO comments.
-
由 Andy Smith 提交于
-
- 04 12月, 2018 1 次提交
-
-
由 aarzilli 提交于
1. Check IsMulticlient and send stop request before doing anything else. 2. Allow init file to call 'exit' Fixes #1430
-
- 28 11月, 2018 1 次提交
-
-
由 zavla 提交于
Fixes an error in wrongly appending os.PathSeparator to source file path on Windows in case of path substitution config option.
-
- 20 11月, 2018 1 次提交
-
-
由 Sergio Lopez 提交于
Instead of unconditionally returning all present goroutines, GoroutinesInfo now allows specifying a range (start and count). In addition to the array of goroutines and the error, it now also returns the next goroutine to be processed, to be used as 'start' argument on the next call, or 0 if all present goroutines have already been processed. This way clients can avoid eating large amounts of RAM while debugging core dumps and processes with a exceptionally high amount of goroutines. Fixes #1403
-
- 20 10月, 2018 1 次提交
-
-
由 Derek Parker 提交于
This patch allows the `trace` CLI subcommand to display return values of a function. Additionally, it will also display information on where the function exited, which could also be helpful in determining the path taken during function execution. Fixes #388
-
- 18 10月, 2018 1 次提交
-
-
由 aarzilli 提交于
The name "where" may confuse users into thinking that this parameter actually does something where in fact it's just arbitrary text used to identify the checkpoint. Fixes #1373
-
- 16 10月, 2018 2 次提交
- 12 10月, 2018 1 次提交
-
-
由 aarzilli 提交于
Support for position independent executables (PIE) on the native linux backend, the gdbserver backend on linux and the core backend. Also implemented in the windows native backend, but it can't be tested because go doesn't support PIE on windows yet.
-
- 11 10月, 2018 1 次提交
-
-
由 Russ Magee 提交于
This change adds a config flag to specify the foreground color of line numbers for the source list command.
-
- 03 10月, 2018 1 次提交
-
-
由 aarzilli 提交于
On macOS 10.14 Apple changed the command line tools so that system headers now need to be manually installed. Instead of adding one extra install step to the install procedure add a build tag to allow compilation of delve without the native backend on macOS. By default (i.e. when using `go get`) this is how delve will be compiled on macOS, the make script is changed to enable compiling the native backend if the required dependencies have been installed. Insure that both configuration still build correctly on Travis CI and change the documentation to describe how to compile the native backend and that it isn't normally needed. Fixes #1359
-
- 26 9月, 2018 2 次提交
-
-
由 aarzilli 提交于
We should print something when we exit from continue/next/step/stepout even if we don't have a source file for the instruction that we are stopped on. This is mostly important on macOS where a SIGSEGV will cause 'continue' to fail with a 'bad access' error (see #852) and the output can be confusing. Fixes #1244
-
由 aarzilli 提交于
-
- 25 9月, 2018 2 次提交
-
-
由 aarzilli 提交于
Instead of failing on the first goroutine we can't read save the error message and keep going. Fixes a bug reported on the mailing list: https://groups.google.com/d/msgid/delve-dev/3b3bfaa3-83d5-4676-b974-1fec40e5bf53%40googlegroups.com?utm_medium=email&utm_source=footer
-
由 chainhelen 提交于
format `whatis <expression>`
-
- 20 9月, 2018 1 次提交
-
-
由 Derek Parker 提交于
Refactors some code, adds a bunch of docstrings and just generally fixes a bunch of linter complaints.
-
- 01 9月, 2018 1 次提交
-
-
由 aarzilli 提交于
Refactors edit and list so that they use the same code to get the current location and also both accept a locspec as an argument.
-
- 31 8月, 2018 1 次提交
-
-
由 aarzilli 提交于
Add a flag to Stackframe that indicates where the stack frame is the bottom-most frame of the stack. This allows clients to know whether the stack trace terminated normally or if it was truncated because the maximum depth was reached. Add a truncation message to the 'stack' command.
-
- 17 8月, 2018 1 次提交
-
-
由 aarzilli 提交于
Updated call description to reflect current limitations.
-
- 01 8月, 2018 1 次提交
-
-
由 Ben Cotterell 提交于
Which I miss from gdb-- it's nice to be able to open where you are in your editor where you're already working on the project you're debugging.
-
- 25 7月, 2018 1 次提交
-
-
由 aarzilli 提交于
Adds -defer flag to the stack command that decorates the stack traces by associating each stack frame with its deferred calls. Reworks proc.next to use this feature instead of using proc.DeferPC, laying the groundwork to implement #1240.
-
- 24 7月, 2018 1 次提交
-
-
由 aarzilli 提交于
next/step/stepout should work even if the current frame isn't the topmost stack frame, but their behavior should be different in that case (they should continue inside the function of the selected frame). Most of the logic of next/step/stepout would work correctly if we simply replaced the call to proc.topframe with something that took a frame index. However the breakpoint they set on the first deferred function is wrong, and fixing it requires scanning the defer stack and matching it to the call stack, something we can't do yet. Given that enhancing next/step/stepout will take time and the current behavior confuses users (see issue #1240) return an error if next/step/stepout are called while the currently selected frame isn't frame 0. Updates #1240
-
- 14 7月, 2018 1 次提交
-
-
由 aarzilli 提交于
Implements the function call injection protocol introduced in go 1.11 by https://go-review.googlesource.com/c/go/+/109699. This is only the basic support, see TODO comments in pkg/proc/fncall.go for a list of missing features. Updates #119
-