How to debug IVF8 DLL

[jimwon]

I had no problem for debugging my compaq CVF6.6 DLL by following instructions on this page http://h18009.www1.hp.com/fortran/kb/q1035.html Now I am using VS.Net2002 with IVF8.0.47. When I tried to debug the DLL the same way, I got the following error message:

Visual Studio can not debug because the debug target "c:ProjectinMyDLL.dll" is not an EXE file.

FYI, I placed my DLL and EXE in the same directories and IVF was in the debug mode. I could not find the place to put "Executable for Debug Session".

Any help would be appreciated.

[jimwon]

Thanks for your response. My question is how and where I set "Executable for Debug Session". My program, EXE in Delphi and DLL in Fortran, worked fine without any problem under VS6 and CVF6.x.My DLLs are compiled successfully under VS.Net and IVF8, but I could not do any run-time debugging and kept getting theerror message in my last post. Thanks.

[jimwon]

Someone please share your knowledge. Thanks.

My EXE is in Delphi and DLL in IVF8 w/ VS.NET 2002 on WinXP Pro.

When I "Start Debug (F5)" in IVF8, I got this error message:

Visual Studio can not debug because the debug target "c:ProjectinMyDLL.dll" is not an EXE file.

My question is how to set "Executable for Debug Session". My program (EXE and DLL) has no compile-time bugs and they were debug-able in CVF6.x.

Thanks a lot.

[Steven_L_Intel1]

Similar to how it is done in CVF. Right click on the project, select Properties. Under Debugging, fill in the path to the executable under Command.

[Nick2]

(fast forward to IVF 9.1)

I'm trying to do the same with a VB6 executable. When I go to debug it, I get "Debugging information for your.exe cannot be found or does not match. Binary was not built with debug information. Do you want to continue debugging?"

(yes)

(mouse over a breakpoint) "The breakpoint will not currently be hit. No symbols have been loaded for this document."

(run the app) and the dll doesn't break at my breakpoints...

[Steven_L_Intel1]

Make sure that the DLL you built, in a debug configuration, is the same as the one you're loading in VB. Make sure that in VB the Debugging option to debug unmanaged code is turned on.

[Nick2]

I fired up good old C++ and used LoadLibraryA...

Turns out the DLL was trying to load EM64Tinlibifcoremdd.dll.....

Why? Got me. I linkedmy dllagainst multithreaded rather than multithreaded dll library andnow debuggingworks

My C++ LoadLibraryA is still complaining of the same. Oh well, at least I pleased the debugger I need.

[Steven_L_Intel1]

Why? Because the DLL libraries are the default when building a DLL. It also suggests that you didn't select the option at install to update the system environment variables. PATH needs to be edited to include the Intel Fortran BIN folder.