mirror of
https://github.com/golang/go
synced 2024-10-05 16:51:21 -06:00
2af0648014
We were not recording function calls as changing the state of memory. As a result, the scheduler was not aware that storing values to the stack in order to make a function call must happen *after* retrieving results from the stack from a just-completed function call. This fixes the container/ring tests. This was my first experience debugging an issue using the HTML output. I'm feeling quite pleased with it. Change-Id: I9e8276846be9fd7a60422911b11816c5175e3d0a Reviewed-on: https://go-review.googlesource.com/13560 Reviewed-by: Keith Randall <khr@golang.org> |
||
---|---|---|
.. | ||
internal | ||
doc.go | ||
main.go |