| commit | 0c4a3b330d03097b729b115df236b37059585ed1 | [log] [tgz] |
|---|---|---|
| author | Tim Peters <tim.peters@gmail.com> | Tue Jul 25 04:07:22 2006 +0000 |
| committer | Tim Peters <tim.peters@gmail.com> | Tue Jul 25 04:07:22 2006 +0000 |
| tree | 8d54a93c31bd60132be9d302cccf1f2aa4bf159e | |
| parent | 4d16b915aa58efc62ed098080fd00c42f5fa0770 [diff] |
current_frames_with_threads(): There's actually no way to guess /which/ line the spawned thread is in at the time sys._current_frames() is called: we know it finished enter_g.set(), but can't know whether the instruction counter has advanced to the following leave_g.wait(). The latter is overwhelming most likely, but not guaranteed, and I see that the "x86 Ubuntu dapper (icc) trunk" buildbot found it on the other line once. Changed the test so it passes in either case.