-
Notifications
You must be signed in to change notification settings - Fork 48
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
random segfault #210
Comments
more information is needed is the crate that you get the fault with available some where or can you print the backtrace from the coredump? |
Which version of summarize are you using? |
I see segfaults when running summarize in release mode off of the stable branch / 10.0.0 tag (6129647), which is what you get when installing as laid out in the README ( The segfault doesn't happen when built with the dev profile on the stable branch, nor when built with the release profile on the master branch. Git bisecting shows that it was fixed by #202. |
No, It's a private project, I no longer have access to the backtrace unfortunately, can try to reproduce. |
I followed the instructions in the readme, seems like @tgnottingham was able to reproduce my experience. |
I am having the same issue - on both a private project, but also a public one.
FYI, removing the |
Stable is now 2 years since its last update, and I just encountered this problem myself. Please update stable or update the docs. |
The stable branch is up-to-date now. We'll look into a way for better taking care of this in the future. |
I tried to use self profile and summarize seems to segfault.
Steps to reproduce:
RUSTFLAGS="-Zself-profile" cargo build
summarize summarize <filename>
Result:
zsh: segmentation fault (core dumped) summarize summarize ...
Additional info
I'm working in a cargo workspace where each member contains a binary and a library
some contain two binaries.
System Info
ArchLinux, kernel 6.4.11-arch2-1
The text was updated successfully, but these errors were encountered: