-
-
Notifications
You must be signed in to change notification settings - Fork 175
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
[BUG] Segfault on start #1096
Comments
Mind sharing the backtrace by running the example with gdb for example? |
Sorry, not experienced with gdb. Is this the right thing?
sufec_gtk is the name of my application. Also, confirmed this doesn't happen on other distributions, which points to it being musl-specific. |
Was this the output of typing |
Sorry, just discovered that command. I'm afraid it doesn't add much
|
I have some other info that might be relevant. I have a similar issue, also musl-specific, on another rust binding crate. That one I traced to being some sort of failure to load the glfw library, as it segfaulted on the first FFI call to it regardless of what that call was (though ldd output on the binary appears correct). Since it seems like this is also happening at the first FFI call, it could be similar. |
I think it's likely the problem is not in gtk4-rs itself, but in some dependency that deals with linking to native libraries. |
See gtk-rs/gtk-rs-core#387 . Toolchain setup problem. |
Ah, I was about to come back and say that the workaround here solved it for me. I'll look at that issue next |
Bug description
When running the hello world example from the crates.io readme I get a segfault at the first step.
Version: 0.4.8
Distribution: Alpine Linux (musl libc)
GTK4 apps on my system work.
The text was updated successfully, but these errors were encountered: