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

segfault on Gentoo #459

Closed
dm9pZCAq opened this issue Dec 21, 2020 · 11 comments
Closed

segfault on Gentoo #459

dm9pZCAq opened this issue Dec 21, 2020 · 11 comments

Comments

@dm9pZCAq
Copy link
Contributor

dm9pZCAq commented Dec 21, 2020

Describe the bug
segfault when trying to launch

To Reproduce
just run gitui

Screenshot
img

Context

  • installed with cargo install gitui
  • OS: Gentoo x86_64
  • GitUI Version: 0.11.0
  • Rust version: 1.47.0

Additional context
when trying to run with --logging log file is empty
but --help show help info without segfault

@extrawurst
Copy link
Owner

hi @dm9pZCAq I personally do not run gentoo. can you build a debug build and check if it is a little more telling? also what I find weird is that the trace looks like you are linking against libgit2 dynamically, that should actually not be the case

@extrawurst extrawurst changed the title segfault segfault on Gentoo Dec 21, 2020
@extrawurst
Copy link
Owner

@dm9pZCAq the repo you try to run in is not public, I assume?

@dm9pZCAq
Copy link
Contributor Author

dm9pZCAq commented Dec 21, 2020

repo is public

but it fails even if gitui is outside of repo

@extrawurst
Copy link
Owner

smells like a gentoo specific issue then :(

@extrawurst
Copy link
Owner

did you check if the last release had the same problems?

@dm9pZCAq
Copy link
Contributor Author

in void linux it is also dynamic linked with libgit (and running without segfault)
libgit

only difference in rust version (void: 1.48)

also when i tried to compile with rust 1.46 there are error in unstable feature
unstable

@extrawurst
Copy link
Owner

also when i tried to compile with rust 1.46 there are error in unstable feature

yeah you need a the latest stable rust

in void linux it is also dynamic linked with libgit (and running without segfault)

dynamically linked libgit is not tested or maintained.

@dm9pZCAq
Copy link
Contributor Author

I took a closer look at the strace and realized that the problem is in the ssl, namely in libressl

and when i removed vendored-openssl feature there it is worked without segfault

but what's strange in the void is also libressl and everything works with vendored-openssl feature

@dm9pZCAq
Copy link
Contributor Author

may be not the best, but there is my solution

@extrawurst
Copy link
Owner

@dm9pZCAq its a stretch but maybe what you observed is due to: rust-lang/git2-rs#645 (comment) - can you check if with the new git2-rs release you still have those issues?

@dm9pZCAq
Copy link
Contributor Author

no

after:

git checkout v0.11.0
cargo update
#    Updating ahash v0.6.1 -> v0.6.2
#    Updating anyhow v1.0.35 -> v1.0.36
#    Updating base64 v0.12.3 -> v0.13.0
#    Updating const_fn v0.4.3 -> v0.4.4
#    Updating git2 v0.13.12 -> v0.13.14
#    Updating indexmap v1.6.0 -> v1.6.1
#    Updating libgit2-sys v0.12.14+1.1.0 -> v0.12.16+1.1.0
#    Updating openssl-src v111.12.0+1.1.1h -> v111.13.0+1.1.1i
#    Updating openssl-sys v0.9.58 -> v0.9.60
#    Updating parking_lot_core v0.8.1 -> v0.8.2
#    Updating quote v1.0.7 -> v1.0.8
#    Updating ron v0.6.3 -> v0.6.4
#    Updating socket2 v0.3.17 -> v0.3.19
#    Updating syn v1.0.54 -> v1.0.55
#    Updating vcpkg v0.2.10 -> v0.2.11
cargo run

i got the same segfault

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants