VS2008 debugger does not give me the IVF compile-time errors

[erik2055]

I have a mixed language VS2008 Solution, with a main project VB.NET calling routines in a second project in IVF.
I can single-step into the Fortran source, and set and use breakpoints in the IVF routines.
So the runtime-debugging is OK.
But when I build the Solution, and there is a compile time error in the Fortran code, it just stops the build and reports that routine XXXXX stopped the build, or something to that effect but NOT telling me the WHY.
No messages about which line or even statement generated the break.

Can I do something about that ?
Would it tell me if I compiled from the command line ? (which I would prefer not to do, because of the single-stepping which I like so much)

[Les_Neilson]

Quoting - erik2055

I have a mixed language VS2008 Solution, with a main project VB.NET calling routines in a second project in IVF.
I can single-step into the Fortran source, and set and use breakpoints in the IVF routines.
So the runtime-debugging is OK.
But when I build the Solution, and there is a compile time error in the Fortran code, it just stops the build and reports that routine XXXXX stopped the build, or something to that effect but NOT telling me the WHY.
No messages about which line or even statement generated the break.

Can I do something about that ?
Would it tell me if I compiled from the command line ? (which I would prefer not to do, because of the single-stepping which I like so much)

Can you attach the build log file showing what messages you did get?
You can compilea file from the command line and still run the IDE afterwards (if it compiles ok and a debug exe is produced on linking).Compiling and debugging are distinct parts of the whole process.

Les

[erik2055]

Quoting - Les Neilson

Can you attach the build log file showing what messages you did get?
You can compilea file from the command line and still run the IDE afterwards (if it compiles ok and a debug exe is produced on linking).Compiling and debugging are distinct parts of the whole process.

Les

Ok: I introduced a spelling error in the Fortran source:
I typed CAL instead of CALL
So building the Solution, I get this in the log:


Compiling with Intel Fortran 11.0.066 [IA-32]...
ifort /nologo /debug:full /Od /I&quotd:lapack-3.1.1" /I&quotd:blas1" /I&quotd:blas2" /I&quotd:blas3" /gen-interfaces /Qdiag-file:&quotDebugdll3.diag" /warn:none /debug-parameters:used /module:&quotDebug" /object:&quotDebug" /traceback /check:bounds /libs:dll /threads /dbglibs /winapp /c /extfor:f /Qvc9 /Qlocation,link,&quotc:Program FilesMicrosoft Visual Studio 9.0VCbin" &quotC:Documents and SettingsErikMy DocumentsVisual Studio 2008ProjectsLAPACKSourcesxerbla.f"
compilation aborted for C:Documents and SettingsErikMy DocumentsVisual Studio 2008ProjectsLAPACKSourcesxerbla.f (code 1)
Dll3 - 1 error(s), 0 warning(s)

Not very informative...
No line number, no mention of a syntax error....

[Steven_L_Intel1]

Looks like an internal compiler error. Can you try the compile from the command line and see if anything more is shown? Can you attach a ZIP file (see below for attachment instructions) with this source and any include/module files it depends on?