Derek Parker 3b2b17938b Improve support for goroutine context switching ... 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.		2014-11-24 17:57:52 -06:00
..
continuetestprog.go	Underscore fixtures dir to ignore during test run	2014-06-09 10:55:18 -05:00
integrationprog.go	Launch prog from cli, also exit cleanly	2014-08-23 08:20:56 -05:00
livetestprog.go	(Mostly) working multithreaded tracing implementation	2014-10-25 08:59:22 -05:00
testnextprog.go	Improve support for goroutine context switching	2014-11-24 17:57:52 -06:00
testprog.go	Implement initial support for stack unwinding.	2014-06-25 14:14:29 -05:00
testthreads.go	(Mostly) working multithreaded tracing implementation	2014-10-25 08:59:22 -05:00
testvariables.go	Improve variable evaluation scope	2014-11-10 21:26:13 -06:00