c533ffe04d
When the runtime collects a stack trace to associate it with some
profiling event (mem alloc, mutex, etc) there is a skip count passed
to runtime.Callers (or equivalent) to skip some known count of frames
in order to get to the "interesting" frame corresponding to the
profile event. Now that the profiling mechanism uses lazy fixup (when
removing compiler artifacts like thunks, morestack calls etc), we also
need to move the frame skipping logic after the fixup, so as to insure
that the skip count isn't thrown off by these artifacts.
Fixes golang/go#32290.
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/179740
From-SVN: r271892
|
||
|---|---|---|
| .. | ||
| aeshash.c | ||
| arch.h | ||
| array.h | ||
| defs.h | ||
| env_posix.c | ||
| getncpu-aix.c | ||
| getncpu-bsd.c | ||
| getncpu-hurd.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-context.S | ||
| 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-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-unsafe-pointer.c | ||
| go-unsetenv.c | ||
| go-unwind.c | ||
| go-varargs.c | ||
| panic.c | ||
| print.c | ||
| proc.c | ||
| rtems-task-variable-add.c | ||
| runtime.h | ||
| runtime_c.c | ||
| stack.c | ||
| yield.c | ||