This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: get windows error message 0xc0000142 on starting cygwin app
On Wed, Sep 19, 2001 at 02:47:43PM +0200, Ralf Habacker wrote:
>> -----Urspr?ngliche Nachricht-----
>> Von: cygwin-apps-owner@sourceware.cygnus.com
>> [mailto:cygwin-apps-owner@sourceware.cygnus.com]Im Auftrag von
>> Christopher Faylor
>> Gesendet am: Mittwoch, 19. September 2001 12:57
>> An: cygwin-apps@cygwin.com
>> Betreff: Re: get windows error message 0xc0000142 on starting cygwin app
>>
>> On Wed, Sep 19, 2001 at 09:26:41AM +0200, Ralf Habacker wrote:
>> >Hi,
>> >
>> >currently I'm compiling kde2 apps with cygwin and xfree and have a problem
>> >loading dll's.
>> >The problem is that on loading the app the windows runtime loader
>> breaks with a
>> >error message
>> >"Die Anwendung konnte nicht richtig initialisiert werden (0xc0000142)"
>> >
>> >gdb says something about an unknown target exception:
>> >--------------------------------------------------------
>> >$ gdb -nw kicker.exe
>> >GNU gdb 5.0 (20010428-1)
>> >(gdb) r
>> >Starting program: /opt/kde2/bin/kicker.exe
>> >gdb: unknown target exception 0xc0000142 at 0x77fb00ac
>> >
>> >Program received signal ?, Unknown signal.
>> >0x77fb00ac in ?? ()
>> >(gdb) q
>> >The program is running. Exit anyway? (y or n) y
>> >--------------------------------------------------------
>> >
>> >I have searched in the microsoft knowledge base, but what I found isn't very
>> >much. :-(
>> >
>> >--------------------------------------------------------
>> >Error Message:
>> >(Application Error) The application failed to initialize properly
>> (0xaddress ).
>> >Click on OK to terminate the application.
>> >User Action:
>> >This is a Windows 2000 Executive STATUS error message. After you
>> terminate the
>> >application, try running it again. If this message reappears, contact the
>> >supplier of the application.
>> >--------------------------------------------------------
>> >
>> >What I have found that this problem occures while the dynamic linker
>> (ntdll) is
>> >working shown below.
>> >The exception is raised by a "leave" instruction, but I
>>
>> Sounds like a corrupted stack.
>>
>You mean, because of loading so many dll's there is an application stack
>overflow ?
No, I mean that an instruction that manipulates the stack results in an
error. That indicates to me that the stack pointer is screwed up.
cgf