- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm using IVF within C++.NET.
(Microsoft Visual C++ .NET 69459-005-5166386-18464, IVF Version 8.1.2613.2003).
I've got a array of derived type declared as
TYPE resp_rec
INTEGER :: rec_num
INTEGER,DIMENSION(MAX_CRITERIA) :: codes
REAL(kind=REAL_DP) :: hhld
REAL(kind=REAL_DP) :: hhld_raw
REAL(kind=REAL_DP) :: pre_weight
REAL(kind=REAL_DP) :: weight
CHARACTER(len=SBII_ID_LEN) :: id
END TYPE resp_rec
TYPE (resp_rec),ALLOCATABLE,DIMENSION(:) :: responses
within a module.
My problem is that when using the debugger's watch window or local variable window, the codes element (the integer array) is displayed fine, as is the rec_num. Nothing else is, especially the element "id", which vaguely resembles line noise.
When these are assigned to 'normal' variables or printed, all is fine.
So...what am I doing wrong?
(Microsoft Visual C++ .NET 69459-005-5166386-18464, IVF Version 8.1.2613.2003).
I've got a array of derived type declared as
TYPE resp_rec
INTEGER :: rec_num
INTEGER,DIMENSION(MAX_CRITERIA) :: codes
REAL(kind=REAL_DP) :: hhld
REAL(kind=REAL_DP) :: hhld_raw
REAL(kind=REAL_DP) :: pre_weight
REAL(kind=REAL_DP) :: weight
CHARACTER(len=SBII_ID_LEN) :: id
END TYPE resp_rec
TYPE (resp_rec),ALLOCATABLE,DIMENSION(:) :: responses
within a module.
My problem is that when using the debugger's watch window or local variable window, the codes element (the integer array) is displayed fine, as is the rec_num. Nothing else is, especially the element "id", which vaguely resembles line noise.
When these are assigned to 'normal' variables or printed, all is fine.
So...what am I doing wrong?
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please provide a complete example and submit it to Intel Premier Support. Note that the version number you gave is not the compiler version, but that of the IDE integration. You can get the compiler version by typing "ifort" at a Fortran command prompt window - it will look something like w_fc_pc_8.1.030.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was using an older version; I upgraded to w_fc_pc_8.1.030 and I'm now getting contents within derived types for module variables.
The problem seems to have gone away.
The problem seems to have gone away.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
... with a lot of help from our debugger engineers!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tell them "thank you".
I've grown to love interactive debuggers, but I can also live without them. My first Fortran program was written on punched cards for a Univac 1108.
I've grown to love interactive debuggers, but I can also live without them. My first Fortran program was written on punched cards for a Univac 1108.
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