- 12 6月, 2015 1 次提交
-
-
由 Derek Parker 提交于
* Set hardware breakpoints on all existing threads * Set hardware breakpoints on any new thread the spawns Fixes #111
-
- 20 4月, 2015 1 次提交
-
-
由 Derek Parker 提交于
* Properly find next source line for goroutines blocked in chanrecv * Refactor breakpoint clearing * Refactor temp breakpoint setting
-
- 25 11月, 2014 1 次提交
-
-
由 Derek Parker 提交于
Remove any assumption that a wait syscall on a thread id after a continue will return. Any time we continue a thread, wait for activity from any thread, because the scheduler may well have switched contexts on us due to syscall entrace, channel op, etc... There are several more things to be done here including: * Potential tracking of goroutine id as we jump around to thread contexts. * Potential of selectively choosing threads to operate on based on the internal M data structures, ensuring that our M has an active G. This commit partially fixes #23 and #24, however there are still some random hangs that happen and need to be ironed out.
-
- 08 11月, 2014 1 次提交
-
-
由 Derek Parker 提交于
-
- 14 10月, 2014 1 次提交
-
-
由 Derek Parker 提交于
Fix bug involving detecting whether or not we have stepped into another function when we plan on return from the function we are currently in.
-
- 13 10月, 2014 1 次提交
-
-
由 Derek Parker 提交于
Once the program detects that we have stepped into another function, we simply calculate the return address and then set a breakpoint and continue to that location, avoiding numerous syscalls.
-
- 10 10月, 2014 1 次提交
-
-
由 Derek Parker 提交于
Needs some refactoring and some optimization, but fixes several bugs.
-
- 04 10月, 2014 1 次提交
-
-
由 Derek Parker 提交于
-
- 20 9月, 2014 1 次提交
-
-
由 Derek Parker 提交于
-
- 19 9月, 2014 1 次提交
-
-
由 Derek Parker 提交于
-
- 11 7月, 2014 1 次提交
-
-
由 Derek Parker 提交于
Improvements: * `next`ing through a loop works correctly (when not already within a loop) * `next`ing out of a function works correctly Needs work: * `next`ing in a loop can be improved when starting within a loop
-
- 07 7月, 2014 1 次提交
-
-
由 Derek Parker 提交于
This current implementation does not cover the following: * Setting correct breakpoint when exiting loop * Setting correct breakpoint when returning from function * All facilities are available for this, it just is not taken into account in the current `next` implementation.
-
- 26 6月, 2014 1 次提交
-
-
由 Derek Parker 提交于
Implement basic api for figuring out, given a current PC value, where the function will return. Currently the API provides only a way to determine the offset from SP (the Canonical Frame Address). It is left up to the caller to grab the actual address from the traced program.
-
- 09 6月, 2014 1 次提交
-
-
由 Derek Parker 提交于
-
- 24 5月, 2014 1 次提交
-
-
由 Derek Parker 提交于
-
- 21 5月, 2014 2 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-