- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a problem viewing composite type variables such of this type
A%B%pointer
Universally I get in debug "Undefined address", when they are defined and the computation works fine - but the debug windows claim it is undefined.
In contrast A%pointer is ok.
Any hints on how to overcome this problem?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any comments?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's hard to comment without knowing what the variable declarations look like.
--Lorri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any declaration. Here is a simple code
type t1
integer, pointer :: c(:)
end type
type t2
type(t1) :: b
end type
type (t2) :: a
type (t1) :: b
ALLOCATE(a%b%c(1),b%c(1))
a%b%c(1)=1
b%c(1)=1
Now if you put a%b%c in QuckWatch it says "Undefined address". This was not a problem in the earlier versions. In contrast if you put b%c in QuckWatch you get no problems,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am not seeing this behavior with the 16.0.0 compiler and VS2013.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tiho, in #4, where was the line pointer (yellow arrow) when you tried to watch the two variables? If on the line containing ALLOCATE, the pointers have not yet been defined, so what you saw ("undefined") is what you should expect.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is what I get.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please attach a ZIP of your project that shows the problem after a build in the 2016 version.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I figured out the problem. The project contained and old *.sln file. I delete that file and on compile a new file is created and after that the is no more problems. I am attaching the example anyway if you want to investigate it. It would be nice if the file is deleted automatically when the project is updated from VS10 to VS13.

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