- 27 9月, 2016 1 次提交
-
-
由 aarzilli 提交于
When a deferred function is called directly Next and StepOut should not step into it. Fixes #582
-
- 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.
-
- 18 3月, 2016 1 次提交
-
-
由 Hubert Krauze 提交于
-
- 17 2月, 2016 1 次提交
-
-
由 aarzilli 提交于
Implements #109 and #120
-
- 24 1月, 2016 1 次提交
-
-
由 aarzilli 提交于
Backend only, no UI Implements #120 (partial)
-
- 10 1月, 2016 1 次提交
-
-
由 Derek Parker 提交于
-
- 09 1月, 2016 1 次提交
-
-
由 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.
-
- 10 10月, 2015 1 次提交
-
-
由 Florin Patan 提交于
This adds support for breakpoints statistics Fixes #247
-
- 27 9月, 2015 1 次提交
-
-
由 Derek Parker 提交于
Only use software breakpoints for now. The reasoning is because it complicates the code without justification, and is only supported on Linux. Eventually, once watchpoints are properly implemented we will revive some of this code. Also, if it is ever necessary to actually set a hw breakpoint we can revive that code as well. All future versions of this code will include support for OSX before being merged back in.
-
- 02 8月, 2015 3 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
- 01 7月, 2015 1 次提交
-
-
由 Derek Parker 提交于
* Cleanup comments * Cleanup naming in certain instances * Modify stacktrace to return current location
-
- 30 6月, 2015 1 次提交
-
-
由 aarzilli 提交于
-
- 29 6月, 2015 1 次提交
-
-
由 aarzilli 提交于
additionally fixes a bug when Detach is called on an exiting/exited thread: dbp.CurrentThread could point to a thread that has already been removed from dbp.Threads by trapWait which will lead to a nil pointer dereference caused proc.Process.clearBreakpoint getting nil from dbp.Threads[tid]
-
- 27 6月, 2015 1 次提交
-
-
由 aarzilli 提交于
-
- 25 6月, 2015 1 次提交
-
-
由 Derek Parker 提交于
For hardware breakpoints we have to set them on every thread. It could be the case that another thread is running. Stop it first, set the breakpoint, then continue it.
-
- 21 6月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 18 6月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 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.
-
- 13 6月, 2015 4 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
Hardware breakpoints are by definition architecture dependant. Move them off the DebuggedProcess struct and onto the associated arch struct.
-
- 12 6月, 2015 1 次提交
-
-
由 Derek Parker 提交于
* Set hardware breakpoints on all existing threads * Set hardware breakpoints on any new thread the spawns Fixes #111
-
- 30 4月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 29 4月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 23 4月, 2015 2 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
- 21 4月, 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
-
- 04 4月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 01 4月, 2015 1 次提交
-
-
由 Derek Parker 提交于
* Better tracking of current goroutine * More efficient, eliminates superfluous step syscalls * Handles concurrency and thread coordination better
-
- 06 3月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 28 2月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 03 2月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 01 2月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 27 1月, 2015 1 次提交
-
-
由 Ellery D'Souza 提交于
-
- 26 1月, 2015 1 次提交
-
-
由 Paul Sbarra 提交于
As of go version 1.4 the standard library syscall package is "locked down" and code outside of the standard library is recommended to migrate to the go.sys subrepository. Reference: https://golang.org/s/go1.4-syscall
-