I used to debug VB 6 binaries using VS 2005 few years back. Now I am trying to do the same in VS 2015 but I am not able to. Could anyone please tell me step by step how can I debug VB 6 binaries in VS 2015?
In your VB6 project's Project->Properties->Compile, check "Compile to Native Code," "No Optimization" and "Create Symbolic Debug Info."
In Visual Studio 2015's Debug->Options, check "Use Native Compatibility Mode":
At runtime, in VS2015, attach to the process containing your VB6 executable. At this point, you should be able to set breakpoints and step through the code.
Related
I am getting this error while compiling my Fortran code in VS Studio:
warning #31001: The dll for reading and writing the pdb (for example, mspdb110.dll) could not be found on your path.
I also looked to change the Base Platform Toolset in Project Properties, but in VS 2019 IDE I couldn't find this option to edit it.
I am using Intel Compiler 2021. I have also tried upgrading my VS Studio to latest version but the problem persists.
Please tell how to fix this.
This message is saying that your Visual Studio is misconfigured. Make sure that you have the "Desktop Development for C++" and "Windows 10 SDK" components of Visual Studio installed (see https://www.intel.com/content/www/us/en/developer/articles/guide/installing-microsoft-visual-studio-2019-for-use-with-intel-compilers.html) You may need to uninstall both the Intel compiler and Visual Studio, then reinstall.
I have a project that is working correctly on Visual studio 2013 Ultimate.
Now we have installed Visual studio 2017 Enterprise.
When I compile and run my project on VS2017 , on several lines of code I receive a strange error message :
"Cannot obtain value of the local variable or argument because it is not
available at this instruction pointer, possibly because it has been optimized away."
What can I do , because on VS2013 I had no problems at all.
Thank you !
uncheck in the project "optimize code"
Also, set the debug info dropdown to full in the advanced options
go to Debug->Options or Tools->Options
and check Debugging->General->Suppress JIT optimization on module load (Managed only)
if you would like a technical reason, you need to post your code
I am using Visual Studio 2013, but I'm in need to develop an old project using the Visual C++ 6.0 compiler.
For this purpose, I have been using Daffodil with no problem on Windows 8.1 for a while.
(You can read more how to use the VC++ 6 compiler in newer Visual Studio versions in this StackOverflow question: Is it possible to use the VC++ 6 compiler in Visual Studio 2012?)
Now I got a new Windows 10 machine, where I reinstalled Visual Studio 6, 2010, 2013 and Daffodil.
Using v60 build tools (Visual C++ 6.0 compiler), project gets compiled fine.
However, when I try to debug, VS says that "debugging information does not match", and I am unable to set breakpoints etc., but:
PDB file is there, same folder and name of debug executable;
Application built in Debug mode, with debug information enabled;
Debugger works fine when using Visual Studio 2010 or 2013 build tools;
Debugger works fine if opening the project inside Visual C++ 6 IDE.
I tried reinstalling all Visual Studio versions as well as Daffodil, but didn't solve.
Any clue what could the problem be?
Finally I actually found a working solution!
for VS 2013:
Enable "Native Edit and Continue"
under Tools->Options->Debugging->Edit and Continue
for VS 2015:
Enable "Use Native Compatibility Mode"
under Tools->Options->Debugging->General
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Compiling a MFC app from Visual Studio 2010 to 2012 RC results in LNK2038
I am moving an XPCOM Firefox add-on project from Visual Studio 2010 to Visual Studio 2012. When I open up the project, Visual Studio asks if I want the project to use the latest C++ compiler. If I say no then I get this compile error:
Error 1 error MSB8020: The builds tools for Visual Studio 2010
(Platform Toolset = 'v100') cannot be found. To build using the v100
build tools, either click the Project menu or right-click the
solution, and then select "Update VC++ Projects...". Install Visual
Studio 2010 to build using the Visual Studio 2010 build
tools. C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.Cpp.Platform.targets 42 5 FF
(Visual Studio 2010)
If I say yes then I get five of these compile errors for xpcomglue_s_nomozalloc.lib in the xulrunner-sdk\lib directory:
error LNK2038: mismatch detected for '_MSC_VER': value '1600' doesn't
match value '1700'
I cannot install Visual Studio 2010. I suppose I could compile Gecko myself, using Visual Studio 2012, although that seems like a lot of work and I'm not sure it will work. So please let me know the best way to compile my Firefox add-on in Visual Studio 2012.
When you are compiling binary XPCOM components you must use the same compiler as used to compile Firefox itself - otherwise the binary compatibility is just not given. Currently this means using Visual C++ 10, be it via the free Visual Studio Express 2010 or by some other means.
If the purpose of the XPCOM component is just to run some native code then you might consider compiling a regular DLL instead and calling it via js-ctypes, then you can use any compiler you like - no binary compatibility constrains (it is also generally recommendable since you no longer need to recompile for each Firefox release).
When I want to start VS10 Ultimate, I get this error:
Title: denenv.exe - Entry Point Not Found
Message : The procedure entry point wmemcpy_s could not be located in the dynamic link library MSVCR100.dll.
There are a couple of files with this name in my Microsoft Visual Studio 10.0 folder.
Which one should I replace, and more important with what version of the file.
Will that solve my problem?
P.S:
OS : Windows 7 x64
Reinstall the Visual C++ Runtime, which you can find in the MS Download Center.
Visual C++ Runtime 2010 (x64)
Visual C++ Runtime 2010 (x68)
I had the same problem, but with vs2012.
I didn't want to borrow a copy from a friend, I have no friends ;).
I tried reinstalling VC++ runtimes for 2010 and 2012, didnt work.
I went to control panel -> programs and features.
right click on Microsoft Visual Studio.
chose repair, that worked for me.
I replaced MSVCR100.dll from %WinDir%/System32 and %WinDir%/SysWOW64 with a version of the file from a friend's computer who had Vs10 installed and properly working.