CodeLite IDE

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

• 0 0x6a9beadc wxObject::wxObject()
  1 0x6a962bb0 wxEvtHandler::wxEvtHandler()
  2 0x00000000 ??

Thanks for any suggestions

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

• 0 0x6a9beadc wxObject::wxObject()
  1 0x6a962bb0 wxEvtHandler::wxEvtHandler()
  2 0x00000000 ??

Thanks for any suggestions

I dont understand, what crashes for you? codelite or the newly built app?
Eran

The App fails to run, sorry should have made that clearer.

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

Eran

I just tested it on a clean machine - works without a problem.
I assume that its something "dirty" in your environment

Eran

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?

Another suggestion:

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)

Eran

Thanks for the suggestion

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?

From:

"Settings -> Debugger Settings -> GNU Debugger -> Misc -> Enable full debugger logging"

Or from the 'Debugger' pane, at the top of the 'Output' view there is a little check box - click it

Eran

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

Debug ...

DEBUG>>=library-loaded,id="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxbase294ud_gcc_cl.dll",target-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxbase294ud_gcc_cl.dll",host-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxbase294ud_gcc_cl.dll",symbols-loaded="0",thread-group="i1"
=library-loaded,id="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxbase294ud_gcc_cl.dll",target-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxbase294ud_gcc_cl.dll",host-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxbase294ud_gcc_cl.dll",symbols-loaded="0",thread-group="i1"
DEBUG>>=library-loaded,id="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxmsw294ud_core_gcc_cl.dll",target-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxmsw294ud_core_gcc_cl.dll",host-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxmsw294ud_core_gcc_cl.dll",symbols-loaded="0",thread-group="i1"
=library-loaded,id="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxmsw294ud_core_gcc_cl.dll",target-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxmsw294ud_core_gcc_cl.dll",host-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxmsw294ud_core_gcc_cl.dll",symbols-loaded="0",thread-group="i1"

Release ...

DEBUG>>=library-loaded,id="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxbase294u_gcc_cl.dll",target-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxbase294u_gcc_cl.dll",host-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxbase294u_gcc_cl.dll",symbols-loaded="0",thread-group="i1"
=library-loaded,id="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxbase294u_gcc_cl.dll",target-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxbase294u_gcc_cl.dll",host-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxbase294u_gcc_cl.dll",symbols-loaded="0",thread-group="i1"
DEBUG>>=library-loaded,id="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxmsw294u_core_gcc_cl.dll",target-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxmsw294u_core_gcc_cl.dll",host-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxmsw294u_core_gcc_cl.dll",symbols-loaded="0",thread-group="i1"
=library-loaded,id="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxmsw294u_core_gcc_cl.dll",target-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxmsw294u_core_gcc_cl.dll",host-name="E:\\x86\\wxWidgets-2.9.4\\lib\\gcc_dll\\wxmsw294u_core_gcc_cl.dll",symbols-loaded="0",thread-group="i1"

All the remaining debug lines are either identical or have the expected differences. What should I be looking for here?