- 25 6月, 2016 1 次提交
-
-
由 aarzilli 提交于
-
- 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.
-
- 14 5月, 2016 1 次提交
-
-
由 Nan Xiao 提交于
Fix typo.
-
- 29 3月, 2016 4 次提交
-
-
由 aarzilli 提交于
proc.(*Thread).Scope fails if we can find a FDE but PCToLine returns nothing
-
由 aarzilli 提交于
-
由 aarzilli 提交于
- made GoroutineStacktrace a method of struct G - made stacktrace a method of StackIterator - renamed StackIterator to stackIterator - factored out logic to obtain a stackIterator from a goroutine that's used by both (*G).Stacktrace and by (*G).UserCurrent
-
由 aarzilli 提交于
Instead of returning an error when FDE of a frame can not be found, just truncate the stack trace. Fixes #462
-
- 18 3月, 2016 1 次提交
-
-
由 Hubert Krauze 提交于
-
- 02 2月, 2016 1 次提交
-
-
由 aarzilli 提交于
-
- 10 1月, 2016 1 次提交
-
-
由 Derek Parker 提交于
-
- 19 10月, 2015 1 次提交
-
-
由 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)
-
- 20 9月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 18 9月, 2015 1 次提交
-
-
由 aarzilli 提交于
stack command: -full flag prints local variables and arguments of all the functions on the stack trace
-
- 06 9月, 2015 1 次提交
-
-
由 aarzilli 提交于
-
- 20 8月, 2015 1 次提交
-
-
由 Derek Parker 提交于
This patch aims to improve how Delve tracks the current goroutine, especially in very highly parallel programs. The main spirit of this patch is to ensure that even in situations where the goroutine we care about is not executing (common for len(g) > len(m)) we still end up back on that goroutine as a result of executing the 'next' command. We accomplish this by tracking our original goroutine id, and any time a breakpoint is hit or a threads stops, we examine the stopped threads and see if any are executing the goroutine we care about. If not, we set 'next' breakpoint for them again and continue them. This is done so that one of those threads can eventually pick up the goroutine we care about and begin executing it again.
-
- 10 8月, 2015 1 次提交
-
-
由 Derek Parker 提交于
Fixes a code path where stacktrace returns < 2 locations and thread.ReturnAddress would panic. Now returns an error.
-
- 02 8月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 29 7月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 17 7月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 10 7月, 2015 1 次提交
-
-
由 Derek Parker 提交于
Major source cleanup, still not finished. Removes gross control flow.
-
- 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 2 次提交
-
-
由 Derek Parker 提交于
-
由 aarzilli 提交于
Finishes #63 #64
-
- 14 6月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 13 6月, 2015 2 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
- 28 5月, 2015 1 次提交
-
-
由 Derek Parker 提交于
Process is an incorrect name for the DebuggedProcess struct that the thread is "a part" of. Also, no need to export that field.
-
- 08 5月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 20 4月, 2015 1 次提交
-
-
由 Derek Parker 提交于
* Properly find next source line for goroutines blocked in chanrecv * Refactor breakpoint clearing * Refactor temp breakpoint setting
-