-
Notifications
You must be signed in to change notification settings - Fork 18
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
Segfaults on Linux #13
Comments
Hi, Thanks for trying out! Ideally, could you try running it in gdb? If it's build with debug symbols it should give you a good stacktrace
|
|
|
OpenGL Renderer: GeForce GTX 960/PCIe/SSE2 |
@itdaniher this seems to be an error with loading the model. Are you executing from the correct directory? I always start up frequensea from the |
@fdb I was too, it's possible I messed up with my gdb invocation.... In any case, I'll try again. Getting frequensea compiled wasn't too bad, and it looks like a very powerful framework for building awesome visualisations! |
Thanks! Good luck and let me know if you get it to work (or if there are any issues). |
|
variant on the theme:
|
Thanks! What backtrace do you get on the FFT example? |
|
The shaders in the Does The two errors / stack traces seem unrelated, though. Unfortunately, I can't reproduce them here (I'm on OS X right now). |
I just tried backporting the shader code to OpenGL 3.2. However, it's not so simple, as the For this to work, I probably need to tweak the API to pass in the shader and the attribute names ( Internally, the text drawing also uses these OpenGL 4 layout specifiers, so that will need to be changed as well. |
!empty.lua doesn't segfault! |
This in mind, I'd be quite happy to see a OpenGL3.2 version of the relevant shaders. I don't know enough about OpenGL to know if it's feasible to upgrade my Debian 9 install to 4.0.... |
I have managed to build latest frequensea on Arch Linux x64 without noticeable problems, but it segfaults upon running:
These are versions of my runtime-related libraries:
What additional info can I provide/how should this be debugged?
The text was updated successfully, but these errors were encountered: