| commit | e324f34afd05c1c47073eec85ee72960e5c3fa53 | |
| author | ian <ian@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Wed, 20 Sep 2017 00:33:29 +0000 (20 00:33 +0000) | ||
| committer | ian <ian@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Wed, 20 Sep 2017 00:33:29 +0000 (20 00:33 +0000) | ||
| tree | e54ea762823ee955d7cd3ef3ae2b8bd4e97b5cf9 | treesnapshot (tar.gz zip) |
| parent | 369a088cda50388058fd496228694c938aa726ec | commitdiff |
runtime: restore "goroutine in C code" message
In the 1.9 upgrade I took out the word "goroutine" from a traceback
showing a goroutine running in C code, to let TestCgoNumGoroutine
pass. However, it turns out that some code is actually checking for
that string; for example,
https://github.com/grpc/grpc-go/blob/master/test/leakcheck/leakcheck.go#L44
So keep the message the same, and change the test.
Reviewed-on: https://go-review.googlesource.com/64850
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@252991 138bc75d-0d04-0410-961f-82ee72b054a4
In the 1.9 upgrade I took out the word "goroutine" from a traceback
showing a goroutine running in C code, to let TestCgoNumGoroutine
pass. However, it turns out that some code is actually checking for
that string; for example,
https://github.com/grpc/grpc-go/blob/master/test/leakcheck/leakcheck.go#L44
So keep the message the same, and change the test.
Reviewed-on: https://go-review.googlesource.com/64850
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@252991 138bc75d-0d04-0410-961f-82ee72b054a4
| gcc/go/gofrontend/MERGE | diffblobblamehistory | |
| libgo/go/runtime/testdata/testprogcgo/numgoroutine.go | diffblobblamehistory | |
| libgo/go/runtime/traceback_gccgo.go | diffblobblamehistory |