We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
go version
go1.8
go env
GOARM=7 GOARCH=arm
I see a SIGSEGV in sigtrampgo, on line 276:
sigtrampgo
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
The text was updated successfully, but these errors were encountered:
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.
Sorry, something went wrong.
No branches or pull requests
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:The relevant disassembly from gdb is
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
The text was updated successfully, but these errors were encountered: