Hi, I have the following problems with IFC 8.1 (Academic License):
I'm unable to use breakpoints in subroutines that use assumed shape arrays. The debugger does not show me the current position in the code and I get no indication that the program has reached a breakpoint. Although i can continue the program with f5 I'm unable to debug such subroutines.
I'm unable to debug global variables defined in modules when used in another module. The debugger does not show their content.
I'm unable to view the content of derived types.
The program freezes often, seems to be related to the assumed shape array problems so the prefered way to exit is kill it from the task manager.
The project is compiled in debug mode, optimizations disabled, my Visual Studio Version is: 7.1.3088
These are severe Problems for my application and I really would appreciate any suggestions on how to solve them. I have attached a small project that illustrates the problem.
Best regards,
Ingo Berg
I'm unable to use breakpoints in subroutines that use assumed shape arrays. The debugger does not show me the current position in the code and I get no indication that the program has reached a breakpoint. Although i can continue the program with f5 I'm unable to debug such subroutines.
I'm unable to debug global variables defined in modules when used in another module. The debugger does not show their content.
I'm unable to view the content of derived types.
The program freezes often, seems to be related to the assumed shape array problems so the prefered way to exit is kill it from the task manager.
The project is compiled in debug mode, optimizations disabled, my Visual Studio Version is: 7.1.3088
These are severe Problems for my application and I really would appreciate any suggestions on how to solve them. I have attached a small project that illustrates the problem.
Best regards,
Ingo Berg
連結已複製
4 回應
Ingo,
Welcome to the forum - but I think you misunderstand its purpose. If you want to report bugs in Intel Fortran, you should do so at Intel Premier Support. This is free - all you have to do is register. This forum is intended to be a user forum for sharing information and getting programming assistance.
I'll look for your report at Premier Support.
Hi Steve,
thanks for your reply. The reason why I posted it here is because I want to now how other people deal with this things in their code. They might be able to show me work arounds or maybe I just used some language features in the wrong way. (Although I would expect the compiler to complain in this case)
I already submitted this to the premium support, but my trust in all kinds of support is fairly limited and I have no illusions that a patch will be issued in the near future if this is indded a bug in the compiler. Although I will be more than happy if I'm proven wrong. The compiler is out for a while I would expect this bug to be already known since there are only basic features involved. After all someone must have realized this before.
Ingo
thanks for your reply. The reason why I posted it here is because I want to now how other people deal with this things in their code. They might be able to show me work arounds or maybe I just used some language features in the wrong way. (Although I would expect the compiler to complain in this case)
I already submitted this to the premium support, but my trust in all kinds of support is fairly limited and I have no illusions that a patch will be issued in the near future if this is indded a bug in the compiler. Although I will be more than happy if I'm proven wrong. The compiler is out for a while I would expect this bug to be already known since there are only basic features involved. After all someone must have realized this before.
Ingo
Have you tried using modulename::variablename in a watch window to look at module variables? This is what is suggested in the documentation.
Some programs do have problems with allocatable variables in the debugger, some don't. If you submitted a test case (I don't see one here), we'll be glad to look at it.
Some programs do have problems with allocatable variables in the debugger, some don't. If you submitted a test case (I don't see one here), we'll be glad to look at it.
Adding the module name does not seem to work for derived types, althoughI now see that they are available. Unfortunatelythey just seem to be filled with trash.Iadded a sample project to the original post, obviousely it didnt appear, I will add it to this post again. (Hope itspossible to attach zip files...) Have a llok at Main.f90 it illustrates the problems.
The example allocates a array of derived type in the module utString and tries to fill it with data in the main program. The debugger does not show the correct entries. The text output confirms that they were set correctly.
Thanks again for your effort,
Ingo
