Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Using release binary on armv7 fails with segmentation fault #6700
I tried upgrading my Gitea Dockerfile for armv7 (based on Alpine) which uses the binary from the release page from 1.7.6 to 1.8.0, but starting Gitea failed.
I was able to reproduce it in an empty alpine container on the armv7 machine by downloading the 1.7.6 binary and executing it - that works without problems, but downloading and executing the 1.8.0 binary fails with a "segmentation fault".
What can be the problem?
Edit: I just tried it in an ubuntu container too, same problem, so it seems like there's something wrong with the binary.
Hi, i got the same problem. I am running Gitea on Xubuntu 18 (odroid platform armv7). The newest 1.8.0 armv7 fails to start with segmentation fault and without any additional comment / stacktrace. I tried with different go versions, but no difference (1.12.1, 1.12.4). It already occured on beta releases 1.8; reverting back to 1.7.5 works fine.
Now i solved the problem like @jlelse did, to use armv6 - works!. But i guess its not the best solution.
For those new to this issue armv6 works.
The issue is apparently something to do with our building environment. The segfault happens extremely early and appears to be when we assign the data segment value main.Version on line 28 however this may simply be first running line of the go program - so I'm not sure whether that's just poor information.
Other putative causes such as glibc version, kernel version have been suggested but I'm not certain about this as people seem to be able to cross-compile without hitting this bug.
Anyway the armv6 binary works for the raspberry pi so that is the suggested workaround until we get some more information.