- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
The idb debugger in the last release of ifort for linux (l_fc_p_10.0.023) doesn't display the module variables.
module mod1
integer mod1_var1
.....
end module mod1
subroutine sub1
use mod1, var1=>mod1_var
var1=1
.....
end
(idb) print var1
best regards
walter steff
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try:
print mod1::var1
print mod1::var1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Steve, thanks for your replay.
I have tried it but "print mod1::var1" seems not to be a legal statement for idb.
Instead it accepts the following command:
print mod1%%mod1_var1
! mod1_var1 was the name of variable defined inside of mod1
but the result doesn't change:
I would like to say that the printing of the module variables worked fine with IFORT 9.1 and Suse 10.0.
Now I have upgraded to IFORT 10.0 and Suse 10.2 which has a newer glibc (2.5).
I have tried to solve the problem by going back to ifort 9.1 but, probably due to the not supported glibc 2.5, idb 9.1 doesn't read any more the debug symbols.
To complete the info I would like to say also that my code is a mix of fortran and C++ and that the idb behaviour doesn't change by switching the linker between ICPC and g++.
best regards
Walter Steffe
I have tried it but "print mod1::var1" seems not to be a legal statement for idb.
Instead it accepts the following command:
print mod1%%mod1_var1
! mod1_var1 was the name of variable defined inside of mod1
but the result doesn't change:
I would like to say that the printing of the module variables worked fine with IFORT 9.1 and Suse 10.0.
Now I have upgraded to IFORT 10.0 and Suse 10.2 which has a newer glibc (2.5).
I have tried to solve the problem by going back to ifort 9.1 but, probably due to the not supported glibc 2.5, idb 9.1 doesn't read any more the debug symbols.
To complete the info I would like to say also that my code is a mix of fortran and C++ and that the idb behaviour doesn't change by switching the linker between ICPC and g++.
best regards
Walter Steffe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please report this problem to Intel Premier Support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok. I will do it
Walter
Walter
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