debug error

[jvandeven]

Hello,

I recently upgraded both a desktop and laptop to VS2015 (community) and Fortran Composer XE 2016.  Everything works fine on the desktop, but the debugger doesn't work on the laptop.  When I attempt to debug the exact same solution on the laptop, I receive the message "Frame not in module", under which there is the message "The current stack frame was not found in a loaded module. Source cannot be shown for this location".  I guess there is a setting somewhere that needs fixing, but I do not know where to start.  Any assistance would be greatly appreciated.

Best regards,

Justin.

[Kevin_D_Intel]

Googling for other instances of "Frame not in module" suggested in some instances this related to some exception handling being enabled.

Maybe try inspecting the Exception settings between the two systems under Debug > Exceptions

[jvandeven]

Thanks for the reply Kevin,

I found that reference on Google as well - I tried playing around with the exceptions, but there are loads of them, and I have no idea how to find which one / ones to alter from the default.  I have checked that the desktop and lap-top use the same exceptions (desktop is set to default, but I have gone through the list for each), and this has had no effect.

Still working away on the problem...

Justin

[Kevin_D_Intel]

Ok. I'll check with our Debugger team and let you know if they have ideas about this.

[Kevin_D_Intel]

I don't know whether the issue will repeat for us, but if you were able to provide a .zip of that solution we could try on our end. You can send me a private reply with the attachment for added security if you wish.

[jvandeven]

It seems to happen with any solution - including the examples shipped with the compiler (e.g. Autodice).  I can, however, debug in 32bit, just not 64 bit.  It may be that my settings have been corrupted at some point.  I tried to do a fresh install yesterday by uninstalling and re-installing both VS and Intel Composer, but the settings I had altered in VS seemed to have been preserved.  

The application I work with only functions effectively with 64bit.  Any further assistance would be greatly appreciated,

Justin.

[Kevin_D_Intel]

Ok, it does sound specific to your particular laptop. I'll pass on the info about 32 vs. 64-bit debugging to see whether that might lead to any ideas from the Debugger team. Unfortunately the earlier messages I shared did not.
 

[jvandeven]

Kevin Davis (Intel) wrote:

Ok, it does sound specific to your particular laptop. I'll pass on the info about 32 vs. 64-bit debugging to see whether that might lead to any ideas from the Debugger team. Unfortunately the earlier messages I shared did not.
 

It turns out that the Autodice example solution runs fine through the debugger in both 32 and 64 bit compiles, when this is done through the VS2010 shell.  The same solution also works through the VS2015 debugger, when compiled in 32bit, but returns the error I note above when compiled in 64bit.  The problem therefore seems to have nothing to do with the solution properties, but is due to some difference between VS2010 and VS2015.  I am unable to track this down further on my end (in part due to my limited understanding of the VS environment settings).  I hope that this problem is resolved at some point in the future...

[Kevin_D_Intel]

Thank you for the continued efforts to identify the root cause and for the additional update.

I expect the answer is yes, but better to ask than assume.

Was the VS2010 Shell installed with a previous Parallel Studio 2015 installation on the laptop?
Does desktop also have VS2010 Shell installed?

I don’t know whether this is be something you are comfortable trying or not, but would it possible to uninstall the Intel Compiler and all our MSVS integrations, then under VS2015 create a trivial C/C++ solution only and see whether the debugging behaves for 32 and 64-bit builds. This might help us understand whether our integrations are at play.

[jvandeven]

I will try this as soon as I have a spare minute and get back to you with results...

[Lijie_T_]

I have the exact same problem with jvandeven. Have you solved it in the end? Thanks.

[jvandeven]

The problem that I note here appeared when I installed Composer XE 2016, selecting the "remove previous compilers" option.  I uninstalled everything, then reinstalled VS2013, Parallel Studio 15.4 (which has extensions for VS2013), and then Parallel Studio 16.0.  The debugger is now working.  Note that I also found it necessary to fix references to the ucrt libraries (in Tools>Options>Intel Compilers>Visual Fortran>Compilers.

Justin

[Kevin_D_Intel]

Thank you for the update and for coming back to share those additional details. Those could prove useful to someone else. I am glad to hear you found a resolution. We will see whether we can reproduce the issue you experienced by replicating your earlier installation choices/flow.

[jvandeven]

This issue appears to have been resolved by recent updates to both VS and VF.  I am not sure which was at fault, but am grateful that things have been resolved.

[Kevin_D_Intel]

Glad to hear this. Based on your other reply about the tabs issue, just to confirm and help others, you now have both VS 2015 Update 1 and PSXE 2016 Update 1 installed and the issue is resolved. Is this correct?

[jvandeven]

Yes, I have VS 2015 update 1 (version 14.0.24720.00), and PSXE 2016 update 1 (version 16.0.1.146).  Everything appears to be operating correctly now.