-
Notifications
You must be signed in to change notification settings - Fork 5
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
mamba binary segmentation fault #57
Comments
Best solution would be to build it from source. I mean even when we try to debug this segmentation fault, I guess we end up in a scenario were we recognise that the binary is un-compatible with your distribution. It may be related to the fluidsynth version used to build the binary, or, any other lib. |
Thanks for the prompt reply. or if I try from with the src directory I get: |
You must download the source with
you could try out Mamba (when it builds successful) as well without install it, by
If you like it you could install it with |
I built it and got the same error. here is the build output |
Do you've jackd up and running? |
Yes, jack is running, same as fluidsynth. |
Strange. I've no idea why it crash for you. Only way to get a hint would be to run a debug build in gdb.
then, when it crash type |
It is odd, I'm using debian stable and testing, not any exotic linux distro. Snd the build went fine, no issues. I'll try the debug process when I got time and post the result. |
Yes, really odd, as I'm using debian as well, unstable/testing here. So our systems wont be much different at all. |
Okay, I erased everything and started from scratch on Debian stable, reinstalled all the dependencies and recompiled, and now it works. It might be that I missed something, although I couldn't tell what. |
Strange. However, nice to hear it works now. |
Thanks for the assistance and for developing this neat software. |
Hello,
I tried mamba binary today on Devuan Daedalus.
I installed libsmf0 (1.3-4) and ran the binary. Got this error message:
Segmentation fault
Without any further indication.
Any suggestions as to how troubleshoot this issue?
The text was updated successfully, but these errors were encountered: