1. 14 3月, 2015 1 次提交
  2. 12 3月, 2015 1 次提交
  3. 08 3月, 2015 1 次提交
  4. 07 3月, 2015 2 次提交
  5. 06 3月, 2015 2 次提交
  6. 02 3月, 2015 1 次提交
  7. 01 3月, 2015 12 次提交
  8. 28 2月, 2015 7 次提交
  9. 18 2月, 2015 1 次提交
  10. 05 2月, 2015 6 次提交
  11. 03 2月, 2015 1 次提交
  12. 02 2月, 2015 1 次提交
    • D
      Fix race between Delve and tracee runtime · e001bbff
      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
      e001bbff
  13. 01 2月, 2015 1 次提交
  14. 27 1月, 2015 1 次提交
  15. 26 1月, 2015 2 次提交