- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A customer is porting an HPC application from a Linux cluster to Windows HPC Server 2008. Now he experiences crashes like this after running the code for a while (in this case: about 30 minutes into the simulation) with the latest v10 Fortran compiler:
forrtl: severe (157): Program Exception - access violation
Image PC Routine Line Source
fds5_parallel.exe 0000000140262347 Unknown Unknown Unknown
fds5_parallel.exe 000000014025FE1B Unknown Unknown Unknown
fds5_parallel.exe 0000000140388A0E Unknown Unknown Unknown
fds5_parallel.exe 0000000140461D54 Unknown Unknown Unknown
fds5_parallel.exe 000000014044392B Unknown Unknown Unknown
kernel32.dll 0000000076FD495D Unknown Unknown Unknown
ntdll.dll 00000000771D8791 Unknown Unknown Unknown
He said he experienced similar crashes in Linux and went for that reason back to the v9 compiler.
Now my questions:
1. What would be a good way to tackle the problem?
2. Does a v10 compiler license contain a downgrade right to a v9 compiler?
3. Can he run a v9 compiler with Visual Studio 2008 (he just bought VS 2008 for this purpose, and the MPI debugger is more stable in VS 2008).
Any other ideas?
Regards,
Steffen
forrtl: severe (157): Program Exception - access violation
Image PC Routine Line Source
fds5_parallel.exe 0000000140262347 Unknown Unknown Unknown
fds5_parallel.exe 000000014025FE1B Unknown Unknown Unknown
fds5_parallel.exe 0000000140388A0E Unknown Unknown Unknown
fds5_parallel.exe 0000000140461D54 Unknown Unknown Unknown
fds5_parallel.exe 000000014044392B Unknown Unknown Unknown
kernel32.dll 0000000076FD495D Unknown Unknown Unknown
ntdll.dll 00000000771D8791 Unknown Unknown Unknown
He said he experienced similar crashes in Linux and went for that reason back to the v9 compiler.
Now my questions:
1. What would be a good way to tackle the problem?
2. Does a v10 compiler license contain a downgrade right to a v9 compiler?
3. Can he run a v9 compiler with Visual Studio 2008 (he just bought VS 2008 for this purpose, and the MPI debugger is more stable in VS 2008).
Any other ideas?
Regards,
Steffen
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1. Build the program with /traceback and/or run it under the debugger to see where it is when it fails. There is most likely a coding error in the application. I would also suggest turning on other diagnostic options such as /check:bounds, /gen-interface and /warn:interface
2. Yes. He will need to have installed 10.1 previously so that the license file is present on the system. The version 9 compiler will not accept a 10.1 serial number.
3. No.
My advice is to debug the problem and not just turn ones back on it. Just because the error does not show when built with v9 that does not mean it's a compiler bug.
2. Yes. He will need to have installed 10.1 previously so that the license file is present on the system. The version 9 compiler will not accept a 10.1 serial number.
3. No.
My advice is to debug the problem and not just turn ones back on it. Just because the error does not show when built with v9 that does not mean it's a compiler bug.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page