- 30 5月, 2016 1 次提交
-
-
由 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.
-
- 25 4月, 2016 1 次提交
-
-
由 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.
-
- 17 2月, 2016 1 次提交
-
-
由 aarzilli 提交于
Implements #109 and #120
-
- 12 2月, 2016 1 次提交
-
-
由 aarzilli 提交于
Implements #368
-
- 25 1月, 2016 1 次提交
-
-
由 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
-
- 10 1月, 2016 1 次提交
-
-
由 Derek Parker 提交于
-
- 09 1月, 2016 2 次提交
-
-
由 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.
-
由 aarzilli 提交于
-
- 16 12月, 2015 1 次提交
-
-
由 aarzilli 提交于
-
- 04 11月, 2015 1 次提交
-
-
由 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
-
- 29 10月, 2015 3 次提交
-
-
由 Derek Parker 提交于
-
由 aarzilli 提交于
-
由 aarzilli 提交于
The new contents of api.Variable are documented in proc/variables.go. Implements #243
-
- 19 10月, 2015 2 次提交
-
-
由 Derek Parker 提交于
-
由 aarzilli 提交于
Three locations are returned for goroutines: its current location, its current location excluding unexported runtime functions and the location of its go instruction. The command 'goroutines' takes a new parameter to select which location to print (defaulting to current location w/o runtime)
-
- 10 10月, 2015 1 次提交
-
-
由 Florin Patan 提交于
This adds support for breakpoints statistics Fixes #247
-
- 20 8月, 2015 1 次提交
-
-
由 Derek Parker 提交于
The shortening of file paths is purely a terminal UI concern. Move that code to the presentation layer, and remove from the service layer.
-
- 13 7月, 2015 1 次提交
-
-
由 Derek Parker 提交于
Allows a user to execute `dlv trace [regexp]` and Delve will execute the program and output information on functions matching [regexp].
-
- 01 7月, 2015 1 次提交
-
-
由 Derek Parker 提交于
* Cleanup comments * Cleanup naming in certain instances * Modify stacktrace to return current location
-
- 30 6月, 2015 1 次提交
-
-
由 aarzilli 提交于
-
- 21 6月, 2015 1 次提交
-
-
由 aarzilli 提交于
Finishes #63 #64
-
- 14 6月, 2015 1 次提交
-
-
由 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.
-