e69d536e81
TestStepConcurrentDirect will occasionally fail (7% of the time on my setup) by either causing the target processs to execute an invalid instruction or (more infrequently) by switching to the wrong thread. Both of those are caused by receiving SIGTRAPs for threads hitting a breakpoint after it has been removed (the thread hits the breakpoint, we stop everything and remove the breakpoint and only after we receive the signal). Change native.(*nativeProcess).stop to handle SIGTRAPs that can't be attributed to a breakpoint, a hardcoded breakpoint in the program's text, or manual stops (and therefore are likely caused by phantom breakpoint hits). Co-authored-by: a <a@kra> |
||
|---|---|---|
| .. | ||
| astutil | ||
| config | ||
| dwarf | ||
| gobuild | ||
| goversion | ||
| locspec | ||
| logflags | ||
| proc | ||
| terminal | ||
| version | ||