This is the mail archive of the
cygwin
mailing list for the Cygwin project.
x32 vs x64 conflict in Application
- From: Sonya Blade <sonyablade2010 at hotmail dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Mon, 7 Oct 2013 07:31:37 +0100
- Subject: x32 vs x64 conflict in Application
- Authentication-results: sourceware.org; auth=none
- References: <DUB119-W345D973E9742F4DF2AAF25C8130 at phx dot gbl>,<DUB119-W33DED429F14356A9C4549DC8130 at phx dot gbl>,<DUB119-W3C7998AF8B48E66A619FCC8130 at phx dot gbl>
DEar All,
I'm receiving the following error ("During startup program exited with code 0xc000007b.")
on application start up(which uses cygwin_32 compiled libraries of Petsc and SLepc ).
I've compiled Petsc and Slepc with Cygwin_32 and tried to test it with code snippet which uses
the Petsc and Slepc libraries which raised x32/x64 error.
Interesting thing is when I loaded the applicaition on dependency walker to test the dependant
dlls and libraries of application I noticed that cygwin1.dll loads kernel32.dll, and cygwin1.dll
is shown as x64 library which it shouldn't be, because I've nowhere used Cygwin_64 for compilation.
Having cygwin1.dll as x64 and kernel32.dll as x86 architecture, can that be a origin of that problem
or is completely normal ?
I attach the snapshot view of dependency walker if it may give you a clue on what actually happens.
http://i40.tinypic.com/9as213.jpg
Your help will be appreciated,