-
Notifications
You must be signed in to change notification settings - Fork 130
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
GL debug warnings emitted from glBlitFramebufferEXT #4
Comments
When i try to use gdb, i have somes errors => http://pastebin.com/JFYWdxsR |
Damn.. I really didn't expect there to be gcc/gdb incompatibilities. Oh well. I guess you could still try and give me a backtrace. For that, do everything as above, but instead of |
Okay Ancurio, the result is here => http://pastebin.com/fKUCiaat :-) |
I think I have an idea of where the problem lies. I'll try to get a patched up version to you soon (after I fix some graphics driver issues I got after upgrading to Fedora19 >_<) for testing. |
Alright, got my graphics drivers in check. Can you try running this executable: http://ancurio.bplaced.net/stuff/mkxp_fboblitfix and see if the warnings are still emitted? |
oops ? Nice error ! ^^" ./mkxp_fboblitfix /ToTheMoon.amd64/mkxp_fboblitfix": not in executable format: File format not recognized |
Yeah... for whatever reason my server space keeps corrupting the executable wtf. Anyway, here's a different mirror that works: http://en.file-upload.net/download-8292575/mkxp_fboblitfix.html |
I'll close this for now as Tikilou seems to have disappeared. |
* MiniFFI: Use MINIFFI_MAX_ARGS instead of literal * MiniFFI: Document lines that need changing if MINIFFI_MAX_ARGS changes * Bump MINIFFI_MAX_ARGS to 12 Fixes mkxp-z#2 * Bump MINIFFI_MAX_ARGS to 16
Console output
Tikilou, I need you to create a core dump at the point where the warnings are emitted. To do that, start the executable through gdb:
gdb ToTheMoon.amd64
set a breakpoint at the debug message proc:
break DebugLoggerPrivate::writeLine
then run the game by typing
r
end pressing enter. Shortly after the game should freeze as the debug point is reached (and the gdb prompt appears again) saying something like "breakpoint 1 reached". Now dump the core:generate-core-file
which will generate a file named "core." (you can quit gdb by entering
q
theny
). Please upload it somewhere and post it here.The text was updated successfully, but these errors were encountered: