- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm really confused with what's happening here. I have a main program using a module:
dum.for:
program stest
use dum
implicit none
integer i
nFluids = 2
allocate(nTemps(2))
nTemps(1) = 3
nTemps(2) = 4
allocate(Fluids(nFluids))
do i = 1, nFluids
allocate(Fluids(i)%DataPoints(nTemps(i)))
enddo
Fluids(1)%DataPoints(1) = 1
Fluids(1)%DataPoints(2) = 2
Fluids(1)%DataPoints(3) = 3
end
and dum_mod.for:
module dum
integer :: nFluids
integer, pointer :: nTemps(:) => null()
type FluidType
sequence
integer, pointer :: DataPoints(:) => null()
end type FluidType
type(FluidType), pointer :: Fluids(:) => null()
end module
So I have 2 fluids, the first has 3 datapoints, the second should have 4 datapoints. When I run these in the debugger, just after the allocation of the Fluids array (before the do loop), if I open up Fluids in the watch window, and then open Fluids(1) and Fluids(2), it already shows 2 datapoint entries for each fluid. Firstly, it shouldn't show any entries there yet, since I haven't allocated the datapoint arrays yet. Secondly, after allocating them it still shows 2 and 2, but there are supposed to be 3 and 4 respectively. Why?
And then, later on when I try to assign values to the datapoints, the first gets its value of 1, but the second doesn't get its value of 2, and of course the 3rd isn't shown.
What's going on here? I upgraded to v28, but still have the problem.
Adrian
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Those smiley faces should be ( : )
bracket colon bracket
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
tags to format code here.
I know there have been some issues looking at allocatable arrays in the debugger that are being worked on. I've seen a problem similar to this before.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
You're not very specific about my problem... I have a real problem now in that I cannot look at these allocatable arrays in the debugger. You don't say whether this is a bug in the debugger or whether I'm doing something wrong.
I am starting a new project and wouldlike use F90 constructs, however if I can't see them in the debugger, that pretty much makes them useless to me, and so I have to go back to F77. Alternatively I have to scrap Intel and go back to CVF.
These are both very big decisions, and I'd appreciate some guidance / workarounds.
Thanks,
Adrian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Something similar, which I have pointed out before...
Isn't there anyone out there but me that misses the capability of the Array Viewer to display arrays with pointer attributes declared in a derived type, like the ones in this example? It works fine in the CVF Array Viewer.
Maybe, it's in the pipeline?
Lars
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

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