Step-by-Step debugging

[stefanborries]

Hello everybody,

I'm using VS2005 on a x386 WindowsXP-Machine with the Intel Fortran 9.1 Compiler and Debugger.
The solution I have consists of different projects in diffrent languages.
All the files have the same Fortran debug settings as the project, which by the way is a library.

When I try to set breakpoints inside the fortran code I always have the trouble that VS2005 tells me there is no sourcecode at the line and I'm asked if I want to go to the Disassemlby window.
Ok, I could do that but I don't want to, I just want to make a Step-By-Step run through the fortran code.

I've already taken a look at the forum but the only solution I found was I should make a new solution and add all the sourcefiles. But I don't want that, cause there are too many files and I'm a little bit too lazy for that.

Thanks for the help...

[Steven_L_Intel1]

Please elaborate on the "different languages". What is the structure of your solution? In what language is the "startup project" of the solution?

[stefanborries]

Different languages:
C++
Fortran

structure of the solution:
I'm not sure what you mean, because I'm relatively new to VS2005 and I'm working with an existing solution I've never seen before.
But I'll try to tell you what I think you want to know. I've got about 20 diffrent projects with countless files in every project. I've got one startup project which is written in C++.

If there is anything else you need to know let me know.

Thanks for your time so far, I hope you or anybody else will be able to help.

[Steven_L_Intel1]

Ok - you have a solution with 20 or so projects, a C++ main program and a bunch of stsatic library projects in C++ and Fortran. Right? How do you get the libraries linked into the executable - do you name the .lib files explicitly or do you set the library projects as dependent projects?

Without seeing your projects, all I can thinkof is that the libraries you're linking in aren't built with debug info (you may be building libraries, but linking in something else.) If you need more help, I suggest filing an issue with Intel Premier Support and attach a ZIP of your solution/projects with all files.

[stefanborries]

Problem is the solution is kind of confidential, so I'm not allowed to zip and send it to anyone.

As far as I see, you are right with the 20 or more projects and so on.

I've chosen full Debuginformation format via properties of the fortran libraries.
The library projects are dependend projects to the executable.
I'm not so sure if I've translated all of the points correctlly since my VS2005 is in german but I hope it may help to narrow down the problem.

Thanks for any help.

[stefanborries]

A small addition.
When I set a breakpoint in a line in the fortran code and start the debugging the breakpoint vanishes inside the sourcecode.
There is still a breakpoint in the list of breakpoints but it's not labled anymore.

[hansr]

Stefan, I often have the same problem, when I forget to switch the Konfiguration from "release" to "debug". Hans

[stefanborries]

Hello Hans,
thanks for the hint but I haven't forgotten to switch from release to debug.

[stefanborries]

I've got a little bit more information that might help.
VS2005 does not create a .pdb or an .idb. That might be a problem, but I'm not sure. Any help is appreciated.
I've created a new solution with a simple 'Hello World' Fortran program which additionally calls a function in a diffrent sourcefile and VS2005 creates a .pdb file and I can debug Step-by-Step without the disassembler.

Next I've created a static library with some Fortran files and compiled them. Guess what! No .pdb, no .idb and again not able to do a Step-By-Step debugging.

Okay. New Information on 06/22/2007. It seems the sourcecode is not stored inside the library, because I cannot switch to Sourcecode at the disassembling breakpoint.

[stefanborries]

Okay seems I have narrowed the problem down.
Here it is:
In fact I can debug fortran code, BUT if there is an include inside the code AND in this include there is a function call to a c-function or c-routine I'm no longer able to debug, because VS2005 tells me it has no sourcecode (of course not, since it is inside the include file).
The question remains, how to solve the problem, but I will open a new thread, because the problem has changed.

Thanks for all the friendly help.