- 24 7月, 2019 1 次提交
-
-
由 Michail Safronov 提交于
* add max-variable-recurse parameter
-
- 20 7月, 2019 1 次提交
-
-
由 Brian de Alwis 提交于
* Add --continue to continue process on launch/attach * Add small test of --continue * regenerate usage docs * minor cleanup * Use similar approach to `trace` and connect and detach using a client instance * back out previous attempt * regen usage doc * fix up continue test * fix TestContinue to properly test --continue * back out unnecessary changes * update faq
-
- 18 7月, 2019 3 次提交
-
-
由 Brian de Alwis 提交于
-
由 Alessandro Arzilli 提交于
If we return ErrProcessExited we should also set exited to true.
-
由 Alessandro Arzilli 提交于
Go 1.13 insists on adding a go version to go.mod, add one that makes sense.
-
- 17 7月, 2019 2 次提交
-
-
由 Alessandro Arzilli 提交于
Add variables flag to mark variables that are allocated on a register (and have no address) and variables that we read as result of a function call (and are allocated on a stack that no longer exists when we show them to the user).
-
由 Alessandro Arzilli 提交于
Increases the maximum string length from 64 to 1MB when loading strings for a binary operator, also delays the loading until it's necessary. This ensures that comparison between strings will always succeed in reasonable situations. Fixes #1615
-
- 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 7 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
Remove dependancy on glide and instead switch completely over to using `go mod vendor` as our vendor solution.
-
由 dpapastamos 提交于
Support for rev {next,step} is not currently implemented.
-
由 Alessandro Arzilli 提交于
Fixes #1598
-
由 Alessandro Arzilli 提交于
Backports debug/dwarf commit: 535741a69a1300d1fe2800778b99c8a1b75d7fdd CL: https://go-review.googlesource.com/18459 The x/debug/dwarf that we used for dwarf/godwarf/type.go was forked from debug/dwarf long before this commit. Original description: Currently readType simultaneously constructs a type graph and resolves the sizes of the types. However, these two operations are fundamentally at odds: the order we parse a cyclic structure in may be different than the order we need to resolve type sizes in. As a result, it's possible that when readType attempts to resolve the size of a typedef, it may dereference a nil Type field of another typedef retrieved from the type cache that's only partially constructed. To fix this, we delay resolving typedef sizes until the end of the readType recursion, when the full type graph is constructed. Fixes #1601
-
- 04 7月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
-
- 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 2 次提交
-
-
由 dpapastamos 提交于
-
由 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.
-
- 28 6月, 2019 1 次提交
-
-
由 David Chase 提交于
Support for bulk queries makes the DWARF quality checker (github.com/dr2chase/dwarf-goodness/cmd/dwarf-goodness) run much more efficiently (replace quadratic cost with linear).
-
- 26 6月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
The location specified '<fnname>:0' could be used to set a breakpoint on the entry point of the function (as opposed to locspec '<fnname>' which sets it after the prologue). Setting a breakpoint on an entry point is almost never useful, the way this feature was implemented could cause it to be used accidentally and there are other ways to accomplish the same task (by setting a breakpoint on the PC address directly).
-
- 24 6月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
Also fixes findCompileUnitForOffset which was broken in some edge cases (when looking up an offset inside the last child of the compilation unit) which don't happen in normal executables (we only look up types, and those are always direct childs of compile units).
-
- 18 6月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
Allow changing the value of a string variable to a new literal string, which requires calling runtime.mallocgc to allocate the string into the target process. This means that a command like: call f("some string") is now supported. Additionally the command: call s = "some string" is also supported. Fixes #826
-
- 16 6月, 2019 1 次提交
-
-
由 Derek Parker 提交于
The bitmasks for transforming a 64-bit register into it's lower-bit counterparts (e.g. RAX -> EAX -> AX -> AH/AL) were incorrect. This patch fixes the bitmasks and adds an additional test.
-
- 13 6月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
Fixes #1578
-
- 12 6月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
Childless compile units would confuse loadDebugInfoMaps. No test because I don't know what causes go to invoke GNU As in such a way that it produces a childless compile unit. Fixes #1572
-
- 05 6月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
Without this a client calling an method on a version of Delve that doesn't have that method (for example because it's old) will never get a response back.
-
- 04 6月, 2019 2 次提交
-
-
由 Alessandro Arzilli 提交于
Fixes #1568
-
由 Alessandro Arzilli 提交于
-
- 01 6月, 2019 2 次提交
-
-
由 Derek Parker 提交于
Prevent conflicts by choosing a name that is extremely unlikely to conflict with any actual package a user may have in their code. Fixes #580
-
由 Alessandro Arzilli 提交于
Instead of reading partial units as we see them skip them entirely and then re-read them when they are imported, directly into the destination compile unit. This avoids a lot of duplicate code in the loadDebugInfoMaps function and will simplify implementing logical breakpoints and support for the new DW_AT_go_package_name attribute added in Go 1.13.
-
- 31 5月, 2019 1 次提交
-
-
由 Sean Chen 提交于
-
- 30 5月, 2019 4 次提交
-
-
由 tschundler 提交于
The current wording is confusing - the file exists and the line exists, so what is the problem? I suspect this ambiguity is behind #1496 and likely others. Also I updated the style to return values like the rest of the code in the file, which is also more readable (IMO and per https://github.com/golang/go/wiki/CodeReviewComments#named-result-parameters)
-
由 Alessandro Arzilli 提交于
* proc: support nested function calls Changes the code in fncall.go to support nested function calls. This changes delays argument evaluation until after we have used the call injection protocol to allocate an argument frame. When evaluating the parse tree of an expression we'll initiate each function call we find on the way down and then complete the function call on the way up. For example. in: f(g(x)) we will: 1. initiate the call injection protocol for f(...) 2. progress it until the point where we have space for the arguments of 'f' (i.e. when we receive the debugCallAXCompleteCall message from the target runtime) 3. inititate the call injection protocol for g(...) 4. progress it until the point where we have space for the arguments of 'g' 5. copy the value of x into the argument frame of 'g' 6. finish the call to g(...) 7. copy the return value of g(x) into the argument frame of 'f' 8. finish the call to f(...) Updates #119 * proc: bugfix: closure addr was wrong for non-closure functions
-
由 Justin Clift 提交于
-
由 Justin Clift 提交于
-
- 24 5月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
Copy the location expression and declaration line of escaped variables when auto-dereferencing them.
-