fanzha02 91e782106e runtime: fix the issue that the -asan option cannot print where the error occurred ... The current -asan option does not print where the error occurred. The reason is that the current implementation calls incorrect asan runtime functions, which do not pass sp and pc where asan runtime functions are called, and report the stack trace from the native code. But asan runtime functions are called from cgo on a separated stack, so it cannot dump the Go stack trace correctly. The correct asan runtime function we should call is __asan_report_error, which will pass sp and pc, and report where the error occurred correctly. This patch fixes this issue. Add the test cases. Fixes #50362 Change-Id: I12ee1d46c7ae069ddef3d23f2fe86e112db60045 Reviewed-on: https://go-review.googlesource.com/c/go/+/374395 Trust: Fannie Zhang <Fannie.Zhang@arm.com> Run-TryBot: Ian Lance Taylor <iant@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>		2021-12-29 04:10:07 +00:00
..
android	all: gofmt more (but vendor, testdata, and top-level test directories)	2021-08-13 20:45:17 +00:00
arm	…
cgo	runtime: fix the issue that the -asan option cannot print where the error occurred	2021-12-29 04:10:07 +00:00
chrome/gophertool	docs: fix case of GitHub	2021-03-05 02:35:21 +00:00
ios	misc/ios: bump min version	2021-12-02 16:48:07 +00:00
linkcheck	all: use bytes.Cut, strings.Cut	2021-10-06 15:53:04 +00:00
reboot	misc/reboot: skip TestRepeatBootstrap on short builders	2021-11-23 16:52:38 +00:00
swig	…
trace	all: use HTML5 br tags	2021-03-13 03:38:42 +00:00
wasm	cmd/link: increase reserved space for passing env on wasm	2021-10-25 20:08:25 +00:00
editors	…
go.mod	cmd/cgo: update to handle ast.IndexListExpr	2021-10-07 18:02:14 +00:00