- 22 4月, 2017 1 次提交
-
-
由 aarzilli 提交于
- move native backend to pkg/proc/native - move gdbserver backend to pkg/proc/gdbserial - move core dumps backend to pkg/proc/core
-
- 19 4月, 2017 1 次提交
-
-
由 aarzilli 提交于
-
- 14 4月, 2017 1 次提交
-
-
由 Alessandro Arzilli 提交于
* proc: Refactor stackIterator to use memoryReadWriter and BinaryInfo * proc: refactor EvalScope to use memoryReadWriter and BinaryInfo * proc: refactor Disassemble to use memoryReadWriter and BinaryInfo
-
- 07 4月, 2017 1 次提交
-
-
由 Alessandro Arzilli 提交于
* proc: refactor BinaryInfo part of proc.Process to own type The data structures and associated code used by proc.Process to implement target.BinaryInfo will also be useful to support a backend for examining core dumps, split this part of proc.Process to a different type. * proc: compile support for all executable formats unconditionally So far we only compiled in support for loading the executable format supported by the host operating system. Once support for core files is introduced it is however useful to support loading in all executable formats, there is no reason why it shouldn't be possible to examine a linux coredump on windows, or viceversa. * proc: bugfix: do not resume threads on detach if killing * Replace BinaryInfo interface with BinInfo() method returning proc.BinaryInfo
-
- 14 3月, 2017 1 次提交
-
-
由 dr2chase 提交于
Stack barriers were removed in Go 1.9, and thus code that expected various stack-barrier-related symbols to exist does not find them. Check for their absence and do not crash when they are missing. Disable stack-barrier-handling test for 1.9 and beyond. Fixes #754.
-
- 23 2月, 2017 1 次提交
-
-
由 aarzilli 提交于
On Windows we can sometimes encounter threads stopped in locations for which we do not have entries in debug_frame. These cases seem to be due to calls to Windows API in the go runtime, we can still produce a (partial) stack trace in this circumstance by following frame pointers (starting with BP). We still prefer debug_frame entries when available since go functions do not have frame pointers before go1.8.
-
- 17 2月, 2017 1 次提交
-
-
由 Alessandro Arzilli 提交于
The PC we have is relative to the first instruction after the CALL instruction currently being executed. Anyone watching a disassembly will understand what's happening if we report the return PC, but reporting the first PC of the current line is useless and confusing.
-
- 09 2月, 2017 2 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
- 08 2月, 2017 1 次提交
-
-
由 Alessandro Arzilli 提交于
* service/rpccommon: fixed typo * proc: test parseG while target is in runtime.deferreturn runtime.deferreturn will change the value of curg._defer.fn in such a way that if the target is stopped at just the right instruction it may crash an incorrect implementation of parseG * proc/stack: handle stack barriers correctly Correctly handle stack barriers insterted during garbage collection.
-
- 20 12月, 2016 1 次提交
-
-
由 aarzilli 提交于
Adds ability to load x87, SSE and AVX registers. Fixes #666
-
- 03 7月, 2016 1 次提交
-
-
- 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.
-