mingw 4.0

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

mingw 4.0

jayshankar nair
Hi ,

I am building exe with Mingw 4.0(Qt 4.6.2 and qwt). I get the following error
"Application failed to initialize correctly.OK to terminate program(0xc).
The application is failing inside ntdll.


I was wondering whether it is related  to using correct mingw header files. The stack trace is attached below. Process explorer show the base address of
dlls don't go beyond the 2GB limit.

Appreciate your help.

Thanks,
Jay





FAULTING_IP:
+176952f00f2df74
00000000 ??              ???
EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00000000
  ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0
FAULTING_THREAD:  00000df8
DEFAULT_BUCKET_ID:  WRONG_SYMBOLS
PROCESS_NAME:  simplus_client.exe
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: ntdll
FAULTING_MODULE: 7c900000 ntdll
DEBUG_FLR_IMAGE_TIMESTAMP:  411096b4
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS
BUGCHECK_STR:  APPLICATION_FAULT_WRONG_SYMBOLS
LAST_CONTROL_TRANSFER:  from 7c93f8f3 to 7c90eb94
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong.
0022fca4 7c93f8f3 c0000005 0022fd30 7c90e1fe ntdll!KiFastSystemCallRet
0022fd1c 7c90eac7 0022fd30 7c900000 00000000 ntdll!RtlInitializeSListHead+0x68e300000000 00000000 00000000 00000000 00000000 ntdll!KiUserApcDispatcher+0x7

STACK_COMMAND:  ~0s; .ecxr ; kb
FOLLOWUP_IP: ntdll!KiFastSystemCallRet+0
7c90eb94 c3              ret
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  ntdll!KiFastSystemCallRet+22fca4
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  ntdll.dll
BUCKET_ID:  WRONG_SYMBOLS
0:000> ~kb
ChildEBP RetAddr  Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
0022fca4 7c93f8f3 c0000005 0022fd30 7c90e1fe ntdll!KiFastSystemCallRet
0022fd1c 7c90eac7 0022fd30 7c900000 00000000 ntdll!RtlInitializeSListHead+0x68e300000000 00000000 00000000 00000000 00000000 ntdll!KiUserApcDispatcher+0x7
0:000> .frame
00 0022fca4 7c93f8f3 ntdll!KiFastSystemCallRet
0:000> kL
ChildEBP RetAddr
WARNING: Stack unwind information not available. Following frames may be wrong.
0022fca4 7c93f8f3 ntdll!KiFastSystemCallRet
0022fd1c 7c90eac7 ntdll!RtlInitializeSListHead+0x68e3
0:000> ub 7c90eac7
ntdll!ZwQueryPortInformationProcess+0xa: 7c90eaba ff12            call    dword ptr [edx]
7c90eabc c3              ret
7c90eabd 90              nop
7c90eabe 90              nop
7c90eabf 90              nop
ntdll!KiUserApcDispatcher:
7c90eac0 8d7c2410        lea    edi,[esp+10h]
7c90eac4 58              pop    eax
7c90eac5 ffd0            call    eax
0:000> ub 0022fd1c
                ^ Unable to find valid previous instruction for 'ub 0022fd1c'
0:000> u 7c90eabd
ntdll!ZwQueryPortInformationProcess+0xd:
7c90eabd 90              nop
7c90eabe 90              nop
7c90eabf 90              nop
ntdll!KiUserApcDispatcher:
7c90eac0 8d7c2410        lea    edi,[esp+10h]
7c90eac4 58              pop    eax
7c90eac5 ffd0            call    eax
7c90eac7 6a01            push    1
7c90eac9 57              push    edi
~


     


------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit.  See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
MinGW-users mailing list
[hidden email]

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Reply | Threaded
Open this post in threaded view
|

Re: mingw 4.0

Lars.Uffmann
jayshankar nair wrote:
> I am building exe with Mingw 4.0(Qt 4.6.2 and qwt). I get the following error
> "Application failed to initialize correctly.OK to terminate program(0xc).
> The application is failing inside ntdll.

Is your error 0xc, or is it 0xc0000005 ? I had that problem because
auto-importing (I still haven't fully understood what that is) fails
without a certain linker setting when building executables with the
latest MinGW packages.

Or almost: If you install the latest binutils-2.20.51 (See recent
posting by Chris Sutcliffe, Message-ID:
<[hidden email]>) then the
correct auto-import behaviour should be active by default and your
problem solved.

Best Regards,

   Lars

--
Dipl.-Ing. Lars Uffmann
Microgravity User Support Center (MUSC)
Deutsches Zentrum für Luft- und Raumfahrt e.V.
Linder Höhe
D-51147 Köln
phone: +49 (0)2203 601 2171
http://www.dlr.de/musc

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit.  See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
MinGW-users mailing list
[hidden email]

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users