My application crashes upon launching it -- wxmsw26u_gcc_custom.dll

[georgie]

I get a crash dialog when I try running an application after compliation.  I'm unsure if this is a bug yet so I was hoping to ask the forum here for some pointers.  I have the following error report from the crash.  I can try to provide some information from a debug session if an obvious answer is not in the offing from someone on this forum.  -- This is a recent behaviour, as of yesterday I was able to compile/run fine.  I can't pinpoint what changed exactly, and I've rebuilt wxwidgets several times to try to get past this issue.  Anyway, thanks in advance, and I can file a bug if noone sees something obvious.


cbibli.exe has encountered a problem and needs to close.  We are sorry for the inconvenience.
Error signature:
AppName: cbibli.exe    AppVer: 0.0.0.0   ModName: wxmsw26u_gcc_custom.dll
ModVer: 2.6.3.0      Offset: 001f3f3a


<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="cbibli.exe" FILTER="GRABMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="cbibli.exe" SIZE="2015438" CHECKSUM="0x9FD8123D" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1EED1C" LINKER_VERSION="0x10000" LINK_DATE="05/31/2006 23:23:01" UPTO_LINK_DATE="05/31/2006 23:23:01" />
    <MATCHING_FILE NAME="wxmsw26u_gcc_custom.dll" SIZE="9691711" CHECKSUM="0x3DF0D751" BIN_FILE_VERSION="2.6.3.0" BIN_PRODUCT_VERSION="2.6.3.0" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x945A1F" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="2.6.3.0" UPTO_BIN_PRODUCT_VERSION="2.6.3.0" LINK_DATE="05/31/2006 22:48:11" UPTO_LINK_DATE="05/31/2006 22:48:11" />
</EXE>
<EXE NAME="wxmsw26u_gcc_custom.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="wxmsw26u_gcc_custom.dll" SIZE="9691711" CHECKSUM="0x3DF0D751" BIN_FILE_VERSION="2.6.3.0" BIN_PRODUCT_VERSION="2.6.3.0" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x945A1F" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="2.6.3.0" UPTO_BIN_PRODUCT_VERSION="2.6.3.0" LINK_DATE="05/31/2006 22:48:11" UPTO_LINK_DATE="05/31/2006 22:48:11" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="983552" CHECKSUM="0x4CE79457" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFF848" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:56:36" UPTO_LINK_DATE="08/04/2004 07:56:36" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

[georgeous]

I launched the debugger and got the following seg fault.  -- hope this helps some.

C:\tmp\Dev\cbibli\Debug>gdb cbibli.exe
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-mingw32"...
(gdb) start
Breakpoint 1 at 0x416f77: file c:/tmp/Dev/wxWidgets/include/wx/intl.h, line 555.

Starting program: C:\tmp\Dev\cbibli\Debug/cbibli.exe

Program received signal SIGSEGV, Segmentation fault.
0x101f3f3a in wxSizer::GetMinSize ()
   from C:\tmp\Dev\cbibli\Debug\wxmsw26u_gcc_custom.dll
(gdb)

[Game_Ender]

You have to actually backtrace (the bt command) once you hit the segfault to get the usefull information.

[georgie]

Thanks.  The problem has been resolved, and it was of course mine.  The xrc i was loading was missing and this was causing the seg fault.  -- I should add some logic to check that the xrc exists prior to loading it.