64 bit debugging not working

64 bit debugging not working

I'm using Intel Visual Fortran Composer XE 2013 SP1 Update 3 and debugging in Visual Studio 2013 Update 2's IDE with this simple program:

    program Console1

    implicit none

    ! Variables
    integer(4) testInt
    ! Body of Console1
    print *, 'Hello World'
    testInt = 7
    end program Console1

When the EXE for this program is compiled with the "IA 32" (the Win32 platform) ifort compiler, the debugging works as expected. The watch on `testInt` changes from a random value to 7.

But, when I use the "Intel (R) 64" (the x64 platform) compiler by setting the project to the x64 platform, the debugger will stop at correct break points. But the watch on `testInt` reports "Undefined address" instead of 7. 

What's going on here? How can I enable correct debugging for 64 bit Fortran compilations? This is interfering with COM Server development where the COM client and server must be 64-bit.

32 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

In the Locals window, what does the "Type" of TESTINT show as? There is not anything special you need to do to enable 64-bit debugging. Are you sure this is a Debug configuration?

Steve - Intel Developer Support

In 32 bit, TESTINT is an INTEGER(4) in the Locals window.
In 64 bit, the "Type" column is empty, and the value is "Undefined Address."

I'm as sure as I can be that it's a Debug configuration. Optimizations are off (/Od) and /debug:full is on.

/nologo /debug:full /Od /warn:interfaces /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc120.pdb" /traceback /check:bounds /check:stack /libs:dll /threads /dbglibs /c

Linker is set flagged /DEBUG:

/OUT:"x64\Debug\Console1.exe" /INCREMENTAL:NO /NOLOGO /MANIFEST /MANIFESTFILE:"C:\Users\Rob\Documents\Visual Studio 2013\Projects\Console1\Console1\x64\Debug\Console1.exe.intermediate.manifest" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /DEBUG /PDB:"C:\Users\Rob\Documents\Visual Studio 2013\Projects\Console1\Console1\x64\Debug\Console1.pdb" /SUBSYSTEM:CONSOLE /IMPLIB:"C:\Users\Rob\Documents\Visual Studio 2013\Projects\Console1\Console1\x64\Debug\Console1.lib"

Compiler output is:

1>------ Rebuild All started: Project: Console1, Configuration: Debug x64 ------
1>Deleting intermediate files and output files for project 'Console1', configuration 'Debug|x64'.
1>Compiling with Intel(R) Visual Fortran Compiler XE 14.0.3.202 [Intel(R) 64]...
1>Console1.f90
1>Linking...
1>Embedding manifest...
1>
1>Build log written to  "file://C:\Users\Rob\Documents\Visual Studio 2013\Projects\Console1\Console1\x64\Debug\BuildLog.htm"
1>Console1 - 0 error(s), 0 warning(s)
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========

Try an uninstall and reinstall of Fortran and see if that helps. If not, I'll suggest other things to try. I don't recall hearing of this particular symptom before.

Steve - Intel Developer Support

I've done that already. The symptom didn't change. 

I can reproduce this after installing VS2013 Update 2. Escalated to development as issue DPD200257062. Right now the only thing I can think of is to revert to VS2013 Update 1.

Steve - Intel Developer Support

You can uninstall Update 2 in Programs and Features > View Installed Updates. If you do that, x64 debugging will return. I'll let you know when I find out more about the problem.

Steve - Intel Developer Support

That worked with the toy program I used. I'll try it now with the COM Server. 

There are upgrade features in Update 2 that I absolutely now need for other development. Is the issue flagged as connected to my Premier account? 

No, it isn't connected to your Premier account. Please enter a Premier issue about this and ask that it be assigned to me. I'll take care of it from there.

Steve - Intel Developer Support

Premier reference number is 6000053249

Got it.

Steve - Intel Developer Support

I have the same problem. Can I be notified when a solution is available?

 

The developers fixed the problem, the fix should appear in update 4. I had asked the developers if they'd be willing to make the fix available separately for affected users, but have not heard back from them. I will ping them on this.

Steve - Intel Developer Support

I've received the fix and tested it. I've already provided it to Robert through Intel Premier Support. Karen, please open an Intel Premier Support issue on this and ask that it be assigned to me, and I'll get you the fix as well. FWIW, the fix also seems to work with the beta 2015 compiler install.

Steve - Intel Developer Support

OK; I'll apply Update 2 to VS2013 and then the DLL. 

Ok I will open an Intel Premier Support issue and have it assigned to you. Thanks.

Karen, if you tell me the issue number once you have it, I can get to it faster.

Steve - Intel Developer Support

I can't seem to submit an issue on Premier Support. No matter what I try on Step 1 "Select Product & Contact" I can't get to the next step. If I enter the product name and hit the Search button nothing happens, if I hit the Next button nothing happens. If I click the "Browse Products" link a window pops up but no products are listed. Is there something I am doing wrong?

Karen, I'll send you a private message to try to help you.

Steve - Intel Developer Support

Hi Steve,

I wish I had discovered this thread before wasting time on VS2013 update 2! Will Composer XE update 4 be released soon?

Cheers, Geoff

Geoff,

Not until August. I will send you a Private Message and attach the fix. Anyone else who wants it is welcome to send me a message and I'll provide it.

Steve - Intel Developer Support

This is a re-post of a private message to Steve so that other forum users can see it...

Sad to say, that fix is not the complete story. Attached is an image that shows an element of a complex type cannot be seen as a sub-structure, but when you break it out on its own, you can see it.

As a secondary issue, the sub-structure "SQLInfo%SQLSchema%fields" is an array which cannot be viewed unless you explicitly identify an element.

I hope you have a fix for this too :)

Cheers, Geoff

Attachments: 

AttachmentSize
Download Watch_image_0.JPG460.92 KB

Hi Steve,

Could you please provide me also with the Fix; I love using Visual Studio and I am not ablt to update Visual Studio because of this issue because in our work we do lot of fortran coding as well. :(

Thanks

Could someone send me the fix?

Me and all my colleagues are stuck on this issue. And funny thing is that there is some problem with messages on Intel side so I can't find out if Steve Lionel received my message.
 

Yes, our messaging system is broken. I'm just going to attach the fix here. Unpack the attached ZIP into C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Packages\Debugger  This will be fixed in Update 4.

Attachments: 

AttachmentSize
Download FEE.zip115.53 KB
Steve - Intel Developer Support

Thank you!
 

Hi Steve,

I've just installed Update 4 and the fix is not in there.

So I copied the FEE.dll from the zip file above in this thread and 64-bit debugging is back to "normal".

Cheers, Geoff

 

Hmm - I had been told it would be in update 4. But I now see that indeed it did not get put into that update - sorry. It is in the 2015/15.0 product.

Steve - Intel Developer Support

All,

I was hoping the replacing of FEE.dll (my copy was dated 2014-04-12) would fix my 32 bit C++/Fortran debugging problem under VS2013.

I had already figured out that I would have to capitalize all variable names and use C++ notation on arrays (eg h2kflags(4) => H2KFLAGS[3]).

My Intel Fortran is Composer XE 2013 Update 4.

I miss hovering over a variable name to get the value or right clicking and Add Watch!

Any other solutions out there? Thanks!

You aren't getting the Fortran debugging support enabled if you have to use C syntax. Is this an all-Fortran application or is there a managed code part?

Steve - Intel Developer Support

Hi,

I have the same problem debugging 64bit applications. All parameters say 'Undefined variable ...'.

Hovering over variables does not show their values, etc.

I'm using 

 

Microsoft Visual Studio Ultimate 2013
Version 12.0.31101.00 Update 4
Microsoft .NET Framework
Version 4.5.51078

Installed Version: Ultimate

Intel(R) Visual Fortran     Package ID: w_fcompxe_2013_sp1.4.237

Intel(R) Visual Fortran Composer XE 2013 SP1 Update 4 Integration for Microsoft Visual Studio* 2013, 14.0.0100.12, Copyright (C) 2002-2014 Intel Corporation
* Other names and brands may be claimed as the property of others.

Intel® C++ Composer XE 2013 SP1   Package ID: w_ccompxe_2013_sp1.4.237
Intel® C++ Composer XE 2013 SP1 Update 4 Integration for Microsoft* Visual Studio* 2013, Version 14.0.1295.12, Copyright © 2002-2014 Intel Corporation. All rights reserved.
* Other names and brands may be claimed as the property of others

Intel® Inspector XE 2013 Update 9   
Intel® Inspector XE 2013 Update 9, (build 328075), Copyright © 2009-2013 Intel Corporation. All rights reserved.

Intel® VTune™ Amplifier XE 2013 Update 15   
Intel® VTune™ Amplifier XE 2013 Update 15, (build 328102), Copyright © 2009-2013 Intel Corporation. All rights reserved.

with the FEE.dll file attached to this thread.

Kind regards,

Sven

Does the Locals window show variables and their types? Show a screenshot.

Steve - Intel Developer Support

Leave a Comment

Please sign in to add a comment. Not a member? Join today