- 02 9月, 2015 1 次提交
-
-
由 Paul Smith 提交于
This change right-aligns the register names in the output of the "regs" command, and pads out the display of the hex value of each register to 16 bytes. This makes scanning registers for set values a bit easier.
-
- 30 8月, 2015 1 次提交
-
-
由 omie 提交于
Support multiple file / directory tables for multiple compilation units. - added a type DebugLines that can hold number of DebugLineInfo - added a supporting attribute to DebugLineInfo called 'Lookup' which is to be used to quickly lookup if file exists in FileNames slice - added supporting methods to lookup and return corresponding DebugLineInfo - changed the debug_line parsing behavior to read all the available tables and push them to DebugLines - since Process.lineInfo is now a slice, it was breaking AllPCsBetween as well - updated that function's definition to accept a new filename parameter to be able to extract related DebugLineInfo - updated calls to AllPCsBetween - fixed tests that were broken due to attribute type change in Process - updated _fixtures/cgotest program to include stdio.h, so that it updates .debug_line header - added a test to check 'next' in a cgo binary - OSX - 1.4 does not support cgo, handle that in new testcase
-
- 28 8月, 2015 2 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
- 22 8月, 2015 2 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
This patch forces Delve to be more mindful of how it handles many threads and the goroutine context switching that occurs in such cases.
-
- 20 8月, 2015 2 次提交
-
-
由 Derek Parker 提交于
Bring similar code up to top level, and keep OS dependant code in OS dependant files. DRY up code a bit.
-
由 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.
-
- 19 8月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 14 8月, 2015 1 次提交
-
-
由 Derek Parker 提交于
We're not dealing with a debugged process having its own controlling terminal at this point, so no need to make the new process a session leader. Simply making the process a group leader will suffice for our purposes at the moment.
-
- 12 8月, 2015 2 次提交
-
-
由 aarzilli 提交于
-
由 Derek Parker 提交于
Fixes a bug on OSX where, if the debugged process spawned a child, when that process received a SIGCHLD it would cause Delve to hang. Fixes #197
-
- 11 8月, 2015 2 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
We don't care, at the process level, whether or not we're single stepping. That state is really only relevant at the thread level.
-
- 10 8月, 2015 3 次提交
-
-
由 Derek Parker 提交于
Fixes a code path where stacktrace returns < 2 locations and thread.ReturnAddress would panic. Now returns an error.
-
由 aarzilli 提交于
This fix helps avoid infinite recursion.
-
由 aarzilli 提交于
-
- 09 8月, 2015 2 次提交
-
-
由 aarzilli 提交于
Breakpoints, tracepoints, etc.. take a location spec as input. This patch improves the expressiveness of that API. It allows: * Breakpoint at line * Breakpoint at function (handling package / receiver smoothing) * Breakpoint at address * Breakpoint at file:line * Setting breakpoint based off regexp
-
由 Derek Parker 提交于
-
- 04 8月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 02 8月, 2015 8 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
- 31 7月, 2015 2 次提交
-
-
由 Derek Parker 提交于
-
由 Michael Gehring 提交于
-
- 30 7月, 2015 2 次提交
-
-
由 Michael Gehring 提交于
-
由 Michael Gehring 提交于
Fixes #192
-
- 29 7月, 2015 7 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 aarzilli 提交于
fixes issue #179
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
- 28 7月, 2015 1 次提交
-
-
由 aarzilli 提交于
the entry point of a function is the beginning of the prologue, which can be run multiple times for each invocation of a function if the stack needs to be expanded or the scheduler needs to be run.
-