I'm sorry. I forgot to mention that I'm not running FO in fullscreen mode. Any ideas how to unhook the keyboard?OndrejR wrote:In last revision 2814 I can turn off fullscreen mode from Options(via custom mode) or comment it in config.xml cause FO run in window mode, but I can't leave FO window. Problem with debugging is that when segfault occurs debugger switch to gdb console. But mouse and keyboard can't leave FO window and that is the problem.
ogre problem when building
Moderator: Oberlus
Re: ogre problem when building
Re: ogre problem when building
EDIT: only via alt-tab it is possible to leave FO window(not from fullscreen).Geoff the Medio wrote:Is that always the case, or just when the segfault occurs?OndrejR wrote:...mouse and keyboard can't leave FO window and that is the problem
Re: ogre problem when building
With gdb I managed to get till chmain.cpp:145 app() before keyboard and mouse were hooked up. At that point there was no segfault, but I couldn't do anything useful.
Edit (15 feb 2009): freeorion.log only prints
Edit (15 feb 2009): freeorion.log only prints
Code: Select all
2009-02-15 19:39:10,020 DEBUG Client : OpenAL initialized. Version 1.1Renderer OpenAL SoftVendor OpenAL Community
Extensions: AL_EXT_EXPONENT_DISTANCE AL_EXT_FLOAT32 AL_EXT_IMA4 AL_EXT_LINEAR_DISTANCE AL_EXT_MCFORMATS AL_EXT_OFFSET AL_LOKI_quadriphonic
2009-02-15 19:39:11,270 DEBUG Client : Limited FPS to 60
Re: ogre problem when building
Could these runtime segfaults be discussed in a separate thread? This thread here is getting out of control...