Installing the Fortran Composer adversely affects C++ program debugging by causing Visual Studio 2013 to crash

Installing the Fortran Composer adversely affects C++ program debugging by causing Visual Studio 2013 to crash

Imagen de Nathan K.

Installing the Fortran Composer adversely affects C++ program debugging by causing Visual Studio 2013 to crash.

I am using Visual Studio 2013 and Intel(R) Visual Fortran Composer XE 2013 SP1 Update 1 Integration for Microsoft Visual Studio* 2013, 14.0.0074.12

After installing Fortran Composer XE 2013 SP1 Update 1 I compile and build a C++ (only) application. When I attempt to use Visual Studio 2013 to debug the program, Visual Studio 2013 terminates unexpectedly (in both Windows 7 and Windows 8) with exception C00000FD (a stack overflow).

This issue seems similar to http://software.intel.com/en-us/forums/topic/488411 and may be related to http://software.intel.com/en-us/forums/topic/487841.

If I uninstall Fortran Composer XE 2013 SP1 Update 1 I can debug C++ applications okay. However, we need to debug Fortran programs too, so uninstalling the Intel product is not a suitable workaround for us.

I was looking forward to upgrading our Fortran compiler and debugging tools, but this issue makes me wary of the risks of upgrading.

Has anyone had this issue and been able to submit it directly to Intel's Product Support team? I hope so because I am having a frustratingly difficult time getting registered to interface directly with Intel’s support.

 

publicaciones de 9 / 0 nuevos
Último envío
Para obtener más información sobre las optimizaciones del compilador, consulte el aviso sobre la optimización.
Imagen de Steve Lionel (Intel)

Hmm - that first thread you linked to is in a forum that I thought would be closed, as it is for a product we no longer sell. (That's the old C++ Windows only Intel Parallel Studio, not the XE version.) That is probably why no Intel person has replied. I'm not familiar with such an issue - I use VS2013 daily - but I'll ask our developers if they have heard of it.

Steve
Imagen de Nathan K.

Thanks for asking your developers Steve.

If I follow the steps to reproduce in the first post in http://software.intel.com/en-us/forums/topic/487841 I can reproduce the behavior described by Inge H. So it seems to me this issue with Visual Studio 2013 crashing is with both Fortran and C++ Studio XE 2013 SP1 Update 1.

Imagen de Steve Lionel (Intel)
Best Reply

The developers already know about this and it is fixed for Update 2, planned for January. It is caused by the support for debugging Intel MIC Architecture (Intel Xeon Phi) applications which is new in Composer XE 2013 SP1. Most of you, I'd guess, don't use this feature. The workaround is:

Rename the two files CPUSideBpManager.vsdconfig and CPUSideRDM.vsdconfig  under “C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Packages\Debugger“  which will disable the MIC VS debugger integration. You could also just delete those.  While this path is for VS2012, you'll find the same files under VS2013. You could also do a "Change" on the Fortran or Parallel Studio XE product in Programs and Features, select Modify and set the "Intel Debugger Extension" to "This will not be installed or removed".

Adjuntos: 

AdjuntoTamaño
Descargar Capture_5.PNG46.61 KB
Steve
Imagen de iliyapolak

So support for MIC debugging caused the stack overflow.

Imagen de Nathan K.

The workaround works swell Steve, thanks!

I would like to clarify a statement in the workaround. The path "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Packages\Debugger" is for Visual Studio 2013. The path "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Packages\Debugger" is for Visual Studio 2012. The version number in the path is the internal version number for Visual Studio, not the number in the product name. Confusing! A table mapping product names to internal version numbers for Visual Studio is here: http://en.wikipedia.org/wiki/Microsoft_Visual_Studio#History

Imagen de Inge H.

Thanks, but why did it take you 3 weeks to get back to the community? I posted this 3 weeks ago http://software.intel.com/en-us/forums/topic/487841 .

Imagen de Steve Lionel (Intel)

Because you posted it in a forum for the wrong product, though I can understand the confusion. I've asked that the "Intel Parallel Studio" forum (not to be confused with Intel Parallel Studio XE, which is a different product) be "archived" so that no new posts go in.  See the sticky topic I added today. I had thought that forum had been closed more than a year ago, and it is not actively monitored.

Steve
Imagen de deberly@geometrictools.com

Cita:

Steve Lionel (Intel) wrote:

Because you posted it in a forum for the wrong product, though I can understand the confusion. I've asked that the "Intel Parallel Studio" forum (not to be confused with Intel Parallel Studio XE, which is a different product) be "archived" so that no new posts go in.  See the sticky topic I added today. I had thought that forum had been closed more than a year ago, and it is not actively monitored.

Thank you for letting us know a workaround.  I started that thread, and this was the first time I visited your forums.  Because the problem arose when I installed an entire service pack, I had no idea which component could be causing the problem.  I decided that I should post to a "general" forum but did not find one for Intel Parallel Studio XE, thus I posted to Intel Parallel Studio.  Your sticky topic will help, because I believe most people who have problems after a full installation might not guess that they need to post to a particular XE forum.

-- Dave Eberly http://www.geometrictools.com

Inicie sesión para dejar un comentario.