Problems debugging 32 bit on Vista 64 bit

[Mark_Jablin]

I recently moved to Windows Vista 64 bit, and I'm having trouble debugging my application for the 32 bit platform. It works properly if I build it for the 64 bit platform.

When I start the debugger, I get this message - The application failed to initialize properly (address).

I opened my application using Dependency Walker, which registers the following complaints:

Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

I have attached a screenshot of my Dependency Walker analysis.

It seems that I need to be dependent on the libraries under the IA32 directory instead of the em64t directory? If that's the case, what am I missing to get it pointed the right way? I have my projects set to use manifests.

Thanks.

[Steven_L_Intel1]

The problem is that the installation of Intel Fortran adds folder(s) for the run-time DLLs to the system PATH environment variable. Depending on the order of these, you may get the 64-bit DLLs found first.

Let me suggest a simple way around this. Open Start > Intel Software Development Tools > Intel Fortran Compiler 10.1 > Build Environment for IA-32 Applications (the wording may say "32-bit" - I don't remember. When the command prompt window opens, type "devenv" and press enter. Visual Studio will start. In this environment you should be able to debug and run your 32-bit applications.

[Mark_Jablin]

Quoting - Steve Lionel (Intel)

The problem is that the installation of Intel Fortran adds folder(s) for the run-time DLLs to the system PATH environment variable. Depending on the order of these, you may get the 64-bit DLLs found first.

Let me suggest a simple way around this. Open Start > Intel Software Development Tools > Intel Fortran Compiler 10.1 > Build Environment for IA-32 Applications (the wording may say "32-bit" - I don't remember. When the command prompt window opens, type "devenv" and press enter. Visual Studio will start. In this environment you should be able to debug and run your 32-bit applications.

Thank you, Steve, that works. Is there a way to set that in a shortcut so I can open with x86 environment with one click?

If not, I should just be able to switch the order of the directories in the system PATH, correct? Our main target will be 32 bit for while to come.

Thanks again.

[Steven_L_Intel1]

You can drag that shortcut to the desktop - that's what I do. You can change PATH, certainly, though then 64-bit Fortran programs may not work.

[jimdempseyatthecove]

Quoting - Mark Jablin

Thank you, Steve, that works. Is there a way to set that in a shortcut so I can open with x86 environment with one click?

If not, I should just be able to switch the order of the directories in the system PATH, correct? Our main target will be 32 bit for while to come.

Thanks again.

How about creating a Batch file that sets PATH and/or other environment variablesthe way you want it thenruns DEVENV. Place a shortcut to this batch file either on the desktop or in Start | Programs |...

Jim Dempsey

[TimP]

Quoting - jimdempseyatthecove

How about creating a Batch file that sets PATH and/or other environment variablesthe way you want it thenruns DEVENV. Place a shortcut to this batch file either on the desktop or in Start | Programs |...

You could use the 32-bit cmd window shortcut command as a model for most of this.