Subroutine ENTRY Arguments "Undefined" in VS2010 Debug View

[jackosullivan1]

I have a subroutine with
ENTRY valvescan(jscan)
where jscan is subsequently used to reference various items in common.


It works ok, but when I breakpoint just below the ENTRY in debug view in VS2010, no value for jscan shows up when I hover thecursor, and it is reported as "Undefined variable jscan" in the Watch 1 window.

If I add the line "idummy=jscan", I can see the value of idummy, but cannot see jscan.

I don't recall this being a problem in VS2005 or 2008.

Have I perhaps missed throwing a switch somewhere that would let VS2010 work right?

Thanks and God bless!
Jack

forgot to mention: using Intel Visual Fortran Composer XE 2011 Update 8 Integration for Microsoft Visual Studio* 2010, 12.1.3520.2010

[Steven_L_Intel1]

I see no difference between VS08 and VS10 in this regard - neither shows ENTRY arguments.

[jackosullivan1]

Thanks, Steve, for the response.

I coulda sworn 2008 worked like I wanted. Maybe it was 2005.

But in any case, shouldn't the argument values be visible/available? I can't use them for triggering breakpoints? Or is the new standard that I have to create local dummy variables for such things? (That does work, of course.)

Thanks again and God bless,
Jack

[Steven_L_Intel1]

I consider this a bug - not sure if it has already been reported. I will find out.

[jackosullivan1]

Thank you, sir.

God bless!
Jack

[jimdempseyatthecove]

>>If I add the line "idummy=jscan", I can see the value of idummy, but cannot see jscan.

It might be better to declare a pointer to jscan (e.g. JSCAN_P). This way the variable(s) will remain live as you step through your program. Using suffix decoration may aid in finding the variable in the watch/locals window.

Jim Dempsey

[jackosullivan1]

Good tips, Jim.

Thanks very much, and of course ...
God bless!
Jack

[Parker_L_]

Hi everyone,

I know this is an old thread but since I am having the exact same issue, and there has been no confirmation that this has already been reported, I am signaling.

I am running VS2010 with Intel 13.0.0.89, on a Win 7 computer.

When inside an ENTRY, and only then, the debugger refuses to let me see any values that are arguments, be it by mousing over the text in the code (no reaction from the debugger), or by adding them to the watch list ("Undefined variable").

Has this been fixed in a more recent release ? Making the debugger useless is well, a pretty MAJOR bug !

*edit : added precision that this does in fact apply only when inside an ENTRY.

[Steven_L_Intel1]

It doesn't sound like the exact same problem, unless you are seeing this only for ENTRY statements.

More likely is that the Fortran debug support is not loading properly. You could try an uninstall and reinstall of the latest version you have access to.

[Parker_L_]

Steve Lionel (Intel) wrote:
It doesn't sound like the exact same problem, unless you are seeing this only for ENTRY statements.

I am only seeing this when inside ENTRYs.

Non-argument arrays and variables are displaying just fine (mouse over gives the values) whether inside an ENTRY or a FUNCTION or a SUBROUTINE without entries.

Argument arrays and variables are displaying just fine (mouse over gives the values) when inside a FUNCTION or SUBROUTINE without entries.

Argument arrays and variables are not displaying (mouse over doesnt trigger anything) / returning "undefined address" (when using spy) when inside an ENTRY.

Hope this helps, as this is quite the show stopper.

[Steven_L_Intel1]

Thanks - it was not clear from your initial post. This problem has been escalated to development as issue DPD200153417. I will follow up here when there is news about it.

[Parker_L_]

Thank you Steve.

With the help of the issue ID you just provided, Google tells me it was already reported as such (by you :)) in early 2010 (see https://software.intel.com/en-us/forums/topic/290636) (an information which hadnt been confirmed in this current thread when I posted).

Since there hadn't been any news from your side since then, should one conclude that no fix has been produced in those 4 years ? Or was there at least a fix produced, but only applied to posterior (post 13.0.0.89) releases ?

Basically, could you state if newer releases are still subject to this bug ?

Thanks for your help.

[Steven_L_Intel1]

It's still not fixed - the notes from the developers suggest that there may be a fundamental limitation in the Microsoft debugger language that blocks viewing ENTRY arguments, but I have asked that another look be taken at this.   Perhaps you can use the stack frame tab or pulldown to look at the caller and see what was passed. Putting on my "Doctor Fortran" hat, I'd comment that ENTRY is an "obsolescent" feature that should not be used in new development, though it is still supported.