Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Annonces
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

debugger can't see host-associated vars in contained subroutines

martymike
Novice
1 376 Visites
I'm just beginning the process of converting from using CVF to IVF 9.1 with Studio 2005.net. I've built a combined C and Fortran project (Fortran main) and the program runs properly for all the tests I've conducted so far. While testing, though, I found that I cannot evaluate host-associated variables while in contained subroutines when stepping through the code in the debugger. I can't believe this is a real bug - it's probably just some setting somewhere, but I can't find it. Anybody know?
0 Compliments
15 Réponses
Steven_L_Intel1
Employé
1 376 Visites
Unfortunately, this is a current restriction. We know about it and hope to resolve it in the near future. You may be able to use the stack frame pulldown to set the context back to the caller to view those variables.
0 Compliments
gabriel_cavallaro
Débutant
1 376 Visites

Hello,

I just jump from CVF to IVF under visual studio .NET. I have the same problem (the variables that are passed to a subroutine appears in watch windows with dummy numbers. But the programs works well).

Is it fix now ? (do we need to install an update)

If it's not, can you explain more precisely the procedure you tell ?

Thanks

Gabriel

0 Compliments
Steven_L_Intel1
Employé
1 376 Visites
I don't think the fix for this has been released yet. If you submit a problem report to Intel Premier Support, we may be able to get you an early copy of the fix.
0 Compliments
Steven_L_Intel1
Employé
1 376 Visites

The particular problem with viewing host-associated variables is understood but not yet fixed. Work is in progress on this. As a workaround you can either:

1) Use the "context" dropdipown in Visual Studio to set the context to the caller where the variable is declared, or
2) If it's a module variable, use the syntax modname::varname in a watch window to view the variable

This works in most cases. We apologize for the inconvenience and hope to fix this soon.

0 Compliments
gabriel_cavallaro
Débutant
1 376 Visites
Thanks for your help and fast reply.
0 Compliments
jackosullivan1
1 376 Visites

Steve,

Has this been fixed in IVF 10.0?

Thanks and God bless!

jackosullivan

0 Compliments
jackosullivan
Débutant
1 376 Visites

I just noticed that Steve is on vacation...

Does anybody know if this has been fixed in IVF10?

Thanks and God bless!

0 Compliments
Jeffrey_A_Intel
Employé
1 376 Visites

Things are better (we think) but there are still some problems to be fixed and work is on-going to fix them. In those cases where we still don't get it right, Steve's work-arounds a few lines up should help.

0 Compliments
jackosullivan
Débutant
1 376 Visites

Jeff,

Thanks for the quick reply and advice. I'm having trouble identifying what is meant by the "Context Dropdown" (using Visual Studio .NET 2003 Service Pack 1). I could find no reference to such in the Help. I was able to switch my way back and forth between the "contain"-ed subroutine and the "contain"-ing subroutine by using the "Call Stack" tab during Debugging. But that isa really tedious way to do things, especially when switching lines in the Call Stack causes the source view to switch to the calling line.

Have I been missing something?

Also, is there any way to sort the variables in the "Locals" window -- or some other window --that would let me locate the variable values quickly?

Thanks again for your help and God bless!

Jack O'Sullivan

0 Compliments
Jeffrey_A_Intel
Employé
1 376 Visites

Sorry for the delay in replying; I'm on the road.

Yes, I believe Steve was referring to the Call Stack window. AndI know it's less than ideal; it's a work-around, not a solution. Be assured we wantthisfixed just as much as you do.

I don't know of any way to change the order in which Visual Studio displays variables in the Locals window. When I'm interested in just a few such variables, I use a Watch window.

0 Compliments
jackosullivan1
1 376 Visites

Jeff,

Thanks very much.

I'll keep lighting those votive candles in front of St. Jude's statue that this problem gets fixed soon.("Saint for impossible causes", you know ;-)

God bless!

jack

0 Compliments
gabriel_cavallaro
Débutant
1 376 Visites

Hello,

Can you tell me if it's now fix ?

Best,

0 Compliments
Steven_L_Intel1
Employé
1 376 Visites
Not yet, but it is being worked on. The problem is quite complex.
0 Compliments
gabriel_cavallaro
Débutant
1 376 Visites

Hello,

Some news ?

Best,

0 Compliments
Steven_L_Intel1
Employé
1 376 Visites
News is the same, but there has been progress. I can't predict when a fix will appear.
0 Compliments
Répondre