- 24 6月, 2015 1 次提交
-
-
由 Derek Parker 提交于
Instead of maintaining two separate client / server implementations, maintain only the more lightweight JSON-RPC service. The reasoning behind the merging of the original HTTP service was ease of tooling, in other words low barrier of entry for external clients (editor integrations, etc...). I believe the JSON-RPC solution still satisfies that constraint while have the advantage of being a more lightweight solution. HTTP, while highly supported in most modern languages, carries with it too many features we would never take advantage of. The RPC architecture seems a more natural approach. The infrastructure set up during the initial HTTP service implementation was leveraged in the JSON-RPC implementation, so if any of those original authors are reading this commit message: thank you for that work, it was not in vain even if though the original HTTP service is not being removed.
-
- 22 6月, 2015 8 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 The Gitter Badger 提交于
-
由 Michael Gehring 提交于
-
由 Derek Parker 提交于
Makes for more deterministic test runs.
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
Fixes #137
-
- 21 6月, 2015 5 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
s/Break/SetBreakpoint/ s/Clear/ClearBreakpoint/ s/BreakByLocation/SetBreakpointByLocation/
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 aarzilli 提交于
Finishes #63 #64
-
- 20 6月, 2015 2 次提交
-
-
由 Derek Parker 提交于
-
由 Giulio Iotti 提交于
-
- 19 6月, 2015 4 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
- 18 6月, 2015 4 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
- 14 6月, 2015 4 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 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 9 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 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.
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
- 12 6月, 2015 3 次提交
-
-
由 Derek Parker 提交于
* Set hardware breakpoints on all existing threads * Set hardware breakpoints on any new thread the spawns Fixes #111
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-