Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Wed, 19 Sep 2001 06:57:22 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: get windows error message 0xc0000142 on starting cygwin app Message-ID: <20010919065722.A12960@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <000501c140dc$6da8b400$651c440a AT BRAMSCHE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000501c140dc$6da8b400$651c440a@BRAMSCHE> User-Agent: Mutt/1.3.21i 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. cgf