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 problem has been escalated to Intel development. In the meantime, I suggest uninstalling Update 2 to VS2013, which you can do through Programs and Features > View Installed Updates. Once that is done, x64 debugging of Fortran programs works again. Further discussion can be found at https://software.intel.com/en-us/forums/topic/515943
Related
I'm using Qt Creator v8.0.1, Qt 6.3.2(MinGW 11.2.0 64-bit), open source version, to develop x64 Windows desktop program and I encountered an assert problem.
Usually, when debugging a program in Qt Creator, if the assert condition in the program is false, the debugger will automatically break at the assert code and we can view calling stack and variables value. If my development environment is on Intel + Windows laptops, which has always been like this.
Recently, I changed to a Mac book Pro M2, equipped Parallel Desktop 18, and installed Windows 11 (on ARM) in Parallel Desktop, and installed Qt Creator v8.0.1, Qt 6.3.2 MinGW 11.2.0 64-bit in windows 11(On ARM). Qt binary is x64 architecure. I debug a program in Qt Creator. If the assert in the program is triggered, I can't view the current function call stack and variable values like I can on Intel+windows environment. Instead, the following message will pop up:
enter image description here
After I click “Retry”, it pops up
enter image description here
It took me a long time to solve this problem，I think it may be that the Qt (x64) debugging function is not adapted well enough on the M2.
Here are some of my attempts:
I installed Visual Studio Community 2022 On ARM in Windows 11 (on ARM) in Parallel Desktop, and Debugging assert works fine in Visual Studio Community 2022.
According to the "(Press Retry to debug the application - JIT must be enabled)" on the dialog, I set Just In Time Debug in Visual Studio, but it doesn't work either.
I set up “GDB Extended” in Qt Creator but it doesn’t work. And it has a great negatively impact on the debugging speed.
I tried to install the Qt for Windows on ARM, bug MinGW 11.2.0 64-bit kit was not supported. (https://doc.qt.io/qt-6/windows.html)
Does anyone know the reason for this problem? Or give some ideas. Thank you.
Is it possible to compile programs for Windows 7 or Windows XP in Visual Studio 2019 on Windows 10?
I have installed Windows 8.1 SDK but it didn't help me. An .exe file doesn't run on windows 7.
What do I need to do to run my program on Windows 7? Adding this rows in my main.cpp also didn't help me.
#include <winsdkver.h>
#define _WIN32_WINNT 0x0601
#include <sdkddkver.h>
Platform tools:
Addititional include directories:
The application error:
0xC000001D: Illegal instruction, which was related to the SSE instruction used in the code. Some new SSE instruction are not implemented at some different CPU.
I suggest you could try to use /arch:IA32 in MSVC compiler options to disable modern CPU instructions.
I have an industrial PC on which I need to install Visual Studio 6.0 . The industrial PC is Windows 7 Professional , 64 bit system.
The error I am getting is "Compatibility issues with this version of Windows". This error is coming on :
1. starting VC++ (twice the msg will be prompted) ,
2. compiling the program (however,the program is compiling after this error msg) but
my program is giving "debug assertion error"
That same program is working perfectly on my laptop which is also 64 bit and Windows 7 Professional and is using Visual Studio 6.0
I have tried disabling the UAC , creating an empty MSJAVA.DLL file , downloading ,registering dx7vb.dll , updating command controls and then installing VC++ in Administrator mode also.
I have also tried changing the compatibility mode to WindowsXP Service Pack2 and running the setup in administrator mode.
I have tried almost all solutions online, but nothing is working for me.
Kindly help.
Take a look in my tool VS6 Installer 4.8 page
http://nuke.vbcorner.net/Articles/VB60/VisualStudio6Installer/tabid/93/language/en-US/Default.aspx
Below the image, you can find then link titled:
For MSDEV.EXE see here
which refere to a tutorial of martin-moene blogspot where explain How To.
Please take note that in this tutorial refert to a very-old version of VS6 Installer 2.1, which isn't longer available and superseded by latest 4.8.
IMPORTANT: you already tried to install MS Visual Studio 6.0, therefore you need BEFORE clean your system (as explained on VS6 Installer page and others tutorials, english ed italian language)
HTH
I have a code which works on turbo c++...However i would like to use it on visual studio c++ 2010 in windows 7. Is there a way to do it...If yes please let me know the same...or else what is the other way to do it...
If you are using headers like "dos.h", "graphics.h" and so on, you won't be able even to compile your project. So, be carefull.
But there is one way to compile and run any of your projects on Windows 7 - you can install some DOS emulator or virtual machine (like VirtualBox) and use 'em for bcpp or tc. The point will be that you will be running emulation of DOS, not the native application. Thereby none of WinNT does not supports native DOS =)
I'm wondering if I can still develop 32-bit apps using a 64-bit machine (64-bit Windows Vista with Visual Studio 2008 SP1)? Because I am planning to buy a laptop with 64-bit Vista. Im asking just to make sure. Thanks!
64-bit Windows runs 32-bit Visual Studio just fine. Unless you specify you wish you use the x64 development tools, it will still compile 32-bit applications.
Straight from the page:
Visual Studio uses the 32-bit cross
compiler even on a Windows 64-bit
computer. You can, however, use devenv
commands to create a command line
environment to call 64-bit hosted
tools.
Further Information: http://msdn.microsoft.com/en-us/library/ms246588(VS.80).aspx
With Visual Studio you are able to target what platform. By default it will run on "Any CPU" (read 32 or 64 bit), but you can specify if you desire. Look under Project>Properties>Build and look for the "Platform Target" property.
Yes. 64-bit vista will run 32-bit executables, so if you have a 32-bit compiler, it will still work.
Within visual studio you can tell it what to compile to under the Configuration Manager - (Build Menu - Configuration manager) - this allows you to target 32 or 64 bit.
64bit of consumer hardwares is usually "amd64" architecture which can run both 32bit apps and 64bit ones natively. Windows Vista 64bit edition supports both 32bit and 64bit system libraries, so basically you can run both type of applications as well. (Note that IA-64 architecture does not allow this.)
Compiling a program in 64bit is not much related to the platform that the compiler runs. But, of course, to run and test the result binary requires the corresponding architecture.
As many mentioned above, VS2008 let you choose the target architecture, so there's no problem.
I've found that just the setup.exe created by Visual Studio 2012 Express won't work on XP, but if you go ahead load MS 4.0 .NET Framework from the Microsoft Website then the *.application will load and install without using the setup.exe at all.