- 01 3月, 2015 11 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
- 28 2月, 2015 8 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
- 24 2月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 18 2月, 2015 8 次提交
-
-
由 Derek Parker 提交于
Currently Travis supports only Ubuntu 12.04 linux 2.6 VMs which are terribly outdated, and trying to track down why it's hanging on Travis but not on other similar VMs is more trouble than it's worth at the moment. Certainly another more appropriate and up to date CI solution should be explored.
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Florin Patan 提交于
-
由 Derek Parker 提交于
-
- 14 2月, 2015 1 次提交
-
-
由 Jackie Li 提交于
-
- 05 2月, 2015 9 次提交
-
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
FDEs previously were loaded into a red/black tree and searched. This is significantly more expensive than a binary search over a slice. Not sure what I was thinking using a red/black tree - this binary search implementation is significantly more efficient.
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 epipho 提交于
-
由 epipho 提交于
-
由 epipho 提交于
-
由 epipho 提交于
-
由 epipho 提交于
-
- 03 2月, 2015 1 次提交
-
-
由 Derek Parker 提交于
-
- 02 2月, 2015 1 次提交
-
-
由 Derek Parker 提交于
This commit fixes a race condition between Delve and the runtime of the traced process. When a new thread is created in the traced process, Delve takes note of it and then continue both the new thread, and the thread that called clone. If Delve attempts to use data in `runtime.allm` before the new `m->procid` is set, errors occur. The errors are due to Delve assuming any m with a procid of 0 is the main thread of the process (due to how theGo runtime allocates M's, only `clone`d threads have procid properly set. This causes certain events (like `next`) to happen twice to the main thread, because 2 m's in `runtime.allm` have a `procid` of 0, and also causes various other issues that prevent proper thread coordination from Delve. Fixes #43
-