Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

runtime: SIGPROF received on g without m #20417

Closed
philhofer opened this issue May 18, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@philhofer
Copy link
Contributor

commented May 18, 2017

What version of Go are you using (go version)?

go1.8

What operating system and processor architecture are you using (go env)?

GOARM=7 GOARCH=arm

I see a SIGSEGV in sigtrampgo, on line 276:

if sp < g.m.gsignal.stack.lo || sp >= g.m.gsignal.stack.hi {

The relevant disassembly from gdb is

   ldr r2, [r10, #24]
=> ldr r3, [r2, #44]

On that line, gdb says r2 is 0. (r10 is g, so r2 is g.m)

Maybe a dup of #10534?

We can reproduce this very consistently when the cpu profiler is turned on.

CC @rakitzis

@philhofer

This comment has been minimized.

Copy link
Contributor Author

commented May 18, 2017

Ah, never mind. Found some suspicious assembly code (ours) that appears to save (and subsequently clobber) r10, so that pointer is probably garbage.

Sorry for the noise.

@philhofer philhofer closed this May 18, 2017

@golang golang locked and limited conversation to collaborators May 18, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.