<feed xmlns='http://www.w3.org/2005/Atom'>
<title>go/src/runtime/testdata/testwinlibthrow/veh.cpp, branch main</title>
<subtitle>Fork of Go programming language with my patches.</subtitle>
<id>http://git.kilabit.info/go/atom?h=main</id>
<link rel='self' href='http://git.kilabit.info/go/atom?h=main'/>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/'/>
<updated>2022-10-20T18:45:28Z</updated>
<entry>
<title>runtime: fix TestVectoredHandlerExceptionInNonGoThread</title>
<updated>2022-10-20T18:45:28Z</updated>
<author>
<name>qmuntal</name>
<email>quimmuntal@gmail.com</email>
</author>
<published>2022-10-20T17:06:05Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=160bb0e66b96e24120deba5fed927acc47b59b1a'/>
<id>urn:sha1:160bb0e66b96e24120deba5fed927acc47b59b1a</id>
<content type='text'>
This test is failing on the windows-arm64-10 builder
https://build.golang.org/log/c161c86be1af83c349ee02c1b12eff5828818f50.

It is not failing on windows-arm64-11, so I guess it has something to
do with the compiler.

This CL simplifies the test so is easier to build.

Change-Id: I6e0e1cf237277628f8ebf892c70ab54cd0077680
Reviewed-on: https://go-review.googlesource.com/c/go/+/444438
TryBot-Result: Gopher Robot &lt;gobot@golang.org&gt;
Reviewed-by: Michael Pratt &lt;mpratt@google.com&gt;
Run-TryBot: Quim Muntal &lt;quimmuntal@gmail.com&gt;
Reviewed-by: Bryan Mills &lt;bcmills@google.com&gt;
</content>
</entry>
<entry>
<title>runtime: ignore exceptions from non-Go threads on windows arm/arm64</title>
<updated>2022-10-19T20:21:26Z</updated>
<author>
<name>qmuntal</name>
<email>quimmuntal@gmail.com</email>
</author>
<published>2022-10-14T15:30:45Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=6fe3ccd74c4bf53552da3d9f59463a8a291f59db'/>
<id>urn:sha1:6fe3ccd74c4bf53552da3d9f59463a8a291f59db</id>
<content type='text'>
If there is no current G while handling an exception it means
the exception was originated in a non-Go thread.

The best we can do is ignore the exception and let it flow
through other vectored and structured error handlers.

I've removed badsignal2 from sigtramp because we can't really know
if the signal is bad or not, it might be handled later in the chain.

Fixes #50877
Updates #56082

Change-Id: Ica159eb843629986d1fb5482f0b59a9c1ed91698
Reviewed-on: https://go-review.googlesource.com/c/go/+/442896
Reviewed-by: Alex Brainman &lt;alex.brainman@gmail.com&gt;
Auto-Submit: Michael Pratt &lt;mpratt@google.com&gt;
TryBot-Result: Gopher Robot &lt;gobot@golang.org&gt;
Reviewed-by: Michael Pratt &lt;mpratt@google.com&gt;
Run-TryBot: Quim Muntal &lt;quimmuntal@gmail.com&gt;
Reviewed-by: David Chase &lt;drchase@google.com&gt;
</content>
</entry>
</feed>
