- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have 100's of modules, all in one file, ALLMODU.FOR
I USE only the modules I need, however I can "see" in the debugger variables in other modules. Why / how is this possible? eg. I have a allocatable array called SNAME in a new module called PVT_MODULE which I check is unallocated before I allocate it. However when I step into this code, SNAME is already allocated. It turns out there is another variable called SNAME in another module I am not USEing. I'm confused why this one is being refered to, not the one in my new module.
I USE only the modules I need, however I can "see" in the debugger variables in other modules. Why / how is this possible? eg. I have a allocatable array called SNAME in a new module called PVT_MODULE which I check is unallocated before I allocate it. However when I step into this code, SNAME is already allocated. It turns out there is another variable called SNAME in another module I am not USEing. I'm confused why this one is being refered to, not the one in my new module.
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, all the debug information is combined in the object file. but the debugger ought to keep these distinct. Can you show us a small test case that demonstrates the pronblem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I tried but it works fine in my small test case. In the meantime I renamed the variable in my module, although it's disconcerting that variables in unUSEd modules make it into the subroutine.
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