Codelite installed from codelite-5.0.6213-mingw4.7.1-wx2.9.4.exe
O/S : Windows 8, 64-bit
Compiler version : gnu g++
I can recreate the issue by following these steps...
1. Create a new project from template "Executable (wxwidgets + wxFB frame)"
2. Compile and link Debug => works fine
3. Compile and link Release => SIGSEGV before app window shown, call stack is as follows
ColinTaylor wrote:Codelite installed from codelite-5.0.6213-mingw4.7.1-wx2.9.4.exe
O/S : Windows 8, 64-bit
Compiler version : gnu g++
I can recreate the issue by following these steps...
1. Create a new project from template "Executable (wxwidgets + wxFB frame)"
2. Compile and link Debug => works fine
3. Compile and link Release => SIGSEGV before app window shown, call stack is as follows
I would check that the correct libraries are being loaded.
Notice that the installer you downloaded was with GCC 4.7.1 this means that *all* your libraries should be built with 4.7.1 (the wx that comes with codelite are built with it)
Make sure that you don't have any other libraries in the path that are being loaded before the ones that codelite installed
Notice that the installer you downloaded was with GCC 4.7.1 this means that *all* your libraries should be built with 4.7.1 (the wx that comes with codelite are built with it)
Make sure that you don't have any other libraries in the path that are being loaded before the ones that codelite installed
The App I am testing is the simple one created by Codelite; it doesn't depend on any of my libraries.
Is there a command I can run to check for 'rogue' libraries in the path?
try running your release version under gdb with full debugger logging enabled
This way you will be able to tell which DLLs are being loaded in the release version (Compare it to the debug version)
try running your release version under gdb with full debugger logging enabled
This way you will be able to tell which DLLs are being loaded in the release version (Compare it to the debug version)
Sadly I don't know how to enable 'full debugger logging', please can you explain?
Thanks for the info on enabling full debugger logging. Sadly I'm none the wiser having compared the output from the debug and release versions, the key difference seems to be