-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
1.1.0 does not start due to a SIGSEGV #1168
Comments
I can't confirm the segmentation violation, https://try.gitea.io running on Alpine works fine, locally testing on macOS works fine and the same for a local Docker container based on ubuntu:16.04. |
And this happens with an empty DB and empty data dirs:
|
+1 for me..
edit: gitea compiled from source works fine, though. |
It seems this is the prebuilt version problem? @tboerger |
Happens to me too on 1.1.0 with the prebuilt binary (linux-amd64):
|
Had the same problem with prebuilt (linux-amd64). And can confirm that compiling gitea from source solves the problem. |
I think this may be a cross compiling bug on Go 1.7 that was fixed on 1.8 I also faced this SIGSEGV error on a private project with 1.7. With 1.8 it doesn't happen. |
But v1.1 is still compiled by Go 1.7 and there is no this question? |
Hi, same problem for me, any workaround ? |
@tboerger maybe we need comiple via go1.8 |
Hi I get this error also from 1.1.1 version get from dl.gitea.io |
Ok with 1.8.1 golang is ok Process followed :
I've got to do also update app.ini as #1378 |
Compiling from source is a totally different story as cross compiling it. Setting my mentioned build flag should already solve the issue on 1.7 |
@tboerger Where did you mention it? |
@freswa on some other similar issues like #1408 (comment) |
@lunny so add |
I have created the pull request #1690 which should solve this issue as it enforces the Go name resolution instead of CGO for cross-compiled binaries. |
@freswa yep, works for me. |
Thx @philfry |
[x]
):Description
Gitea does not start since updating to 1.1.0 (prebuild version from release page)
The text was updated successfully, but these errors were encountered: