Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29275 Discussions

Closing Program produces unhandled exception after porting from CVF to IVF

onkelhotte
New Contributor II
1,017 Views

Hi there,

finally our company bought the new IVF10 compiler. Im using VS2003 C++ as IDE with WindowsXP SP2 32-bit as OS.
After I ported my current CVF QuickWin project to IVF it produces an unhandled exception when I end the program. It doesnt matter if I end it normally with end program or stop.

The error message is:
Unbehandelte Ausnahme bei 0x005a0872
(unhandled exception at 0x005a872)

The line is in crt0.c line 251:
mainret = WinMain(
#endif /* WPRFLAG */
GetModuleHandleA(NULL),
NULL,
lpszCommandLine,
StartupInfo.dwFlags & STARTF_USESHOWWINDOW
? StartupInfo.wShowWindow
: SW_SHOWDEFAULT
);

Has anybody encountered this problem before?

Thanks in advance,
Markus

0 Kudos
5 Replies
Steven_L_Intel1
Employee
1,017 Views
This does not look familiar to me. Please submit an issue to Intel Premier Support and attach both your CVF project and the IVF project.
0 Kudos
Markus_P_
Beginner
1,017 Views

I think this is a VS2003 problem: Starting the exe from the explorer produces no exeption, only when I start the program in VS2003.

Shall I submit the two projects to Premier Support anyway?

Thanks in advance,
Markus

0 Kudos
Steven_L_Intel1
Employee
1,017 Views
Is it a debug-configuration executable? When you start it in VS are you doing so with or without debugging? Which set of libraries is it linked against? What happens when you run it from a command prompt window started with Start > Programs > Microsoft Visual Studio.NET 2003 > Visual Studio.NET Tools > Command Prompt?
0 Kudos
onkelhotte
New Contributor II
1,017 Views

Myprojectproduces a crash in Debug and Release mode when I start the program through VS. It does not matter if i start the program or start with debug.

But I can start the Debug and Release mode executable from Windows Explorer, the command prompt and the VScommand promptwithout a crash.

Runtime Library is "Debug QuickWin (/libs:qwin /dbglibs)" for Debugand "QuickWin (/libs:qwin)" for Release mode.
Additional Dependencies are "kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib" and "dfconsol.lib" is ignored.

I use VisualStudio C++.NET Version 2003 with Microsoft Visual Studio .NET 2003 Service Pack 1 (KB918007)and Microsoft Visual Studio .NET 2003 Hotfix (KB927696) installed.

Markus

0 Kudos
Steven_L_Intel1
Employee
1,017 Views
Interesting. Sounds like you're getting a different DLL from the VS environment compared to running directly. Download Dependency Walker and start it from the VS2003 command prompt, then have it open your executable. Record the list and paths of DLLs found. Repeat this for running from an ordinary command prompt and compare.
0 Kudos
Reply