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
WX-3.0 must be built with "-DNDEBUG" #117
Comments
Fixes scp-fs2open#117 Visual Studio doesn't seem to care either way, so %ld it is.
23d96d3 should resolve this issue. |
No the issue is still there. I applied 23d96d3, built on Debian/amd64 & WX-3.0 without "-DNDEBUG" and got the following crash:
|
What do you have on line 77 of code/MainWindow.cpp? I have:
|
Same thing. |
DEBUG=off (default) now shows splash screen on startup due to being on the same #if NDEBUG bandwagon used to turn off verbose logging. GitHub: scp-fs2open/wxLauncher#117 PR: 199919 Submitted by: lightside <lightside@gmx.com> (maintainer) git-svn-id: svn+ssh://svn.freebsd.org/ports/head@385443 35697150-7ecd-e111-bb59-0022644237b5
DEBUG=off (default) now shows splash screen on startup due to being on the same #if NDEBUG bandwagon used to turn off verbose logging. GitHub: scp-fs2open/wxLauncher#117 PR: 199919 Submitted by: lightside <lightside@gmx.com> (maintainer)
0.9.6 release resolves this issue. |
this still happens to me as of current git d56c6de wx 3.0.2 ASSERT INFO: BACKTRACE: |
DEBUG=off (default) now shows splash screen on startup due to being on the same #if NDEBUG bandwagon used to turn off verbose logging. GitHub: scp-fs2open/wxLauncher#117 PR: 199919 Submitted by: lightside <lightside@gmx.com> (maintainer)
With WX-3.0 wxLauncher must be built with "-DNDEBUG" (which was default with WX-2.8).
When built without "-DNDEBUG" wxlauncher segfaults on second start when
~/.wxlauncher/global.ini
exists:It is very counter-intuitive that is necessary to build with "-DNDEBUG" on WX-3.0 and it is not mentioned anywhere.
Perhaps build system should be modified to handle NDEBUG build flag automatically?
The text was updated successfully, but these errors were encountered: