- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi,
I have a fortran project that uses a C library. When debugging into the C library the debugger wants to shows all variables in Fortran style which means it does not any value. I cannot access pointers and all variables will be shown as undefined variables.
How can I debug mixed language (Fortran calls C-lib) applications?
Regards,
Ingo
I have a fortran project that uses a C library. When debugging into the C library the debugger wants to shows all variables in Fortran style which means it does not any value. I cannot access pointers and all variables will be shown as undefined variables.
How can I debug mixed language (Fortran calls C-lib) applications?
Regards,
Ingo
링크가 복사됨
5 응답
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
I've never had a problem doing this. It could be that the "expression evaluator switcher" is incorrectly installed on your system.
Open C:Program FilesMicrosoft Visual Studio .NET 2003Common7PackagesDebugger, right click on NatDbgEE.dll, select Properties, Version. What is the description and version number shown?
Open C:Program FilesMicrosoft Visual Studio .NET 2003Common7PackagesDebugger, right click on NatDbgEE.dll, select Properties, Version. What is the description and version number shown?
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi,
I just found out that the problem is even worse. Even in a pure C++ project all variables are shown in fortran style. Which unltimately means the debugger does not show any meaningfull information.
The NatDbgEE.dll Version is 9.0.2603.2003
This is the Beta version of the Compiler, but the very same problem was described earlier for Version 8.1:
http://softwareforums.intel.com/ids/board/message?board.id=5&message.id=12939&highlight=debugger+c%2B%2B#M12939
I submitted this as issue 307048.
Regards
Ingo
I just found out that the problem is even worse. Even in a pure C++ project all variables are shown in fortran style. Which unltimately means the debugger does not show any meaningfull information.
The NatDbgEE.dll Version is 9.0.2603.2003
This is the Beta version of the Compiler, but the very same problem was described earlier for Version 8.1:
http://softwareforums.intel.com/ids/board/message?board.id=5&message.id=12939&highlight=debugger+c%2B%2B#M12939
I submitted this as issue 307048.
Regards
Ingo
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Since you are currently using a beta compiler, please continue this with Intel Premier Support.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Sorting out issues with the premier support usually means:
"We come back to you" and nothing happens. I have submitted some bug reports and I always try to provide sample projects that reproduce the issue. But even getting the support people to reproduce an issue with the existing project file can be hard.
I can imagine that those people, are sometimes having a hard time being in the "frontline" of user support. But from my end it seems like I'm wasting my time with all those issue submissions. The premier support could not help me with any substantial issue and im anxiousely downloading every new update just to realize that the only changes are new compiler switches that I would call "esotheric" features at best.
Anyway
Ingo
"We come back to you" and nothing happens. I have submitted some bug reports and I always try to provide sample projects that reproduce the issue. But even getting the support people to reproduce an issue with the existing project file can be hard.
I can imagine that those people, are sometimes having a hard time being in the "frontline" of user support. But from my end it seems like I'm wasting my time with all those issue submissions. The premier support could not help me with any substantial issue and im anxiousely downloading every new update just to realize that the only changes are new compiler switches that I would call "esotheric" features at best.
Anyway
Ingo
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
I'm sorry to hear this - it is not a typical experience. I'll look at your issues and see what is going on.