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

Jump to bottom

runtime: crash at startTheWorldWithSema #17317

Closed
thincal opened this issue Oct 2, 2016 · 4 comments
Closed

runtime: crash at startTheWorldWithSema #17317

thincal opened this issue Oct 2, 2016 · 4 comments
Labels
FrozenDueToAge

Comments

@thincal
Copy link

thincal commented Oct 2, 2016

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

1.7

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

ubuntu14.04

What did you do?

I have a program written by Go, which is running to monitor the folder content and do something.
Normally it's working very well, but today I get a coredump file for this program.

What did you see instead?

There is a crash happened:

Thread 1 (LWP 1274):
#0  runtime.raise () at /home/tools/go/src/runtime/sys_linux_arm.s:137
#1  0x0004d734 in runtime.dieFromSignal (sig=6) at /home/tools/go/src/runtime/signal1_unix.go:195
#2  0x0004d8d4 in runtime.crash () at /home/tools/go/src/runtime/signal1_unix.go:272
#3  0x00039238 in runtime.dopanic_m (gp=0x107010e0, pc=231208, sp=275958224) at /home/tools/go/src/runtime/panic.go:684
#4  0x0006ab60 in runtime.dopanic.func1 () at /home/tools/go/src/runtime/panic.go:553
#5  0x0006f0c4 in runtime.systemstack () at /home/tools/go/src/runtime/asm_arm.s:247
#6  0x0003d6a4 in runtime.startTheWorldWithSema () at /home/tools/go/src/runtime/proc.go:1036
#7  0x0003d728 in runtime.mstart () at /home/tools/go/src/runtime/proc.go:1096
#8  0x10700960 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

From the crash call stack, there isn't any info related with my program, could you help check is it a crash caused by the runtime ? many thanks.
@minux
Copy link
Member

minux commented Oct 2, 2016 via email

@thincal
Copy link
Author

thincal commented Oct 2, 2016

it is from a core dump.

@thincal
Copy link
Author

thincal commented Oct 2, 2016

Do you mean the panic is happened inside the runtime or the application code invoke the panic ? If it is the app code call the panic somewhere, there should show the function from app in this call stack, right?

Thanks.

@quentinmit
Copy link
Contributor

Unfortunately, the core dump does not contain enough information to know what caused the panic. It likely was caused by your application or a library it called, but we just don't know without seeing the output that was printed on stderr. Issue #16893 will add the panic logs to the core dump, so in the future we'll be able to tell you more.

Closing this issue since there isn't anything actionable we can do with this traceback.

@golang golang locked and limited conversation to collaborators Oct 4, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@quentinmit @minux @thincal @gopherbot