- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a project compiled with ifort-11.0. These days I have transplant it to ifort-12.1. But when I run it, it went wrong. And show "forrtl: severe (173) ...". How can I understand this? And when I debug it with gdb. Gdb exit.
Link Copied
6 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Error 173 is "A pointer passed to DEALLOCATE points to an array that cannot be
deallocated". You can debug using idb and add -traceback to the compile to get source and line information that may help you find the error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Why 11.0 can do, but 12.1 cann't?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there any way to ignorethis different?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No - you have a bug in your program that needs to be fixed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I used idb to debug my program. The idb output box show "Cannot run thread, error #COULDNT_READ_REGISTER_VALUE". And I reboot system, and then it worked ok. If don't reboot system, how to fix this problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My guess is that you have some part of the program writing memory where it shouldn't, or an uninitilized variable is being used. The first thing I would suggest is to rebuild the program with "-warn interface -C" and see if any errors are reported.
My guess is that a debug version won't show the problem, but at least try building with -traceback to see if you can identify where in the code it is failing. Analysis using the Static Analysis feature of Intel Fortran Studio or Intel Parallel Studio XE could also be helpful.
My guess is that a debug version won't show the problem, but at least try building with -traceback to see if you can identify where in the code it is failing. Analysis using the Static Analysis feature of Intel Fortran Studio or Intel Parallel Studio XE could also be helpful.

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