Ian Lance Taylor f0d89c7759 runtime: avoid write barriers with traceback info ... Unlike the gc runtime, libgo stores traceback information in location structs, which contain strings. Therefore, copying location structs around appears to require write barriers, although in fact write barriers are never important because the strings are never allocated in Go memory. They come from libbacktrace. Some of the generated write barriers come at times when write barriers are not permitted. For example, exitsyscall, marked nowritebarrierrec, calls exitsyscallfast which calls traceGoSysExit which calls traceEvent which calls traceStackID which calls trace.stackTab.put which copies location values into memory allocated by tab.newStack. This write barrier can be invoked when there is no p, causing a crash. This change fixes the problem by ensuring that location values are copied around in the tracing code with no write barriers. This was found by fixing the compiler to fully implement //go:nowritebarrierrec; CL to follow. Reviewed-on: https://go-review.googlesource.com/134226 From-SVN: r264282		2018-09-13 17:30:00 +00:00
..
aeshash.c
arch.h
array.h
defs.h
env_posix.c
getncpu-aix.c
getncpu-bsd.c
getncpu-irix.c
getncpu-linux.c
getncpu-none.c
getncpu-solaris.c
go-assert.c
go-assert.h
go-caller.c
go-callers.c
go-cdiv.c
go-cgo.c
go-construct-map.c
go-ffi.c
go-fieldtrack.c
go-libmain.c
go-main.c
go-matherr.c
go-memclr.c
go-memcmp.c
go-memequal.c
go-memmove.c
go-nanotime.c
go-nosys.c
go-now.c
go-reflect-call.c
go-runtime-error.c
go-setenv.c
go-signal.c
go-string.h
go-strslice.c
go-type.h
go-typedesc-equal.c
go-unsafe-pointer.c
go-unsetenv.c
go-unwind.c
go-varargs.c
panic.c
print.c
proc.c
rtems-task-variable-add.c
runtime_c.c
runtime.h
stack.c
thread.c
yield.c