Why does the program assemble, but do nothing? - visual-studio

Here is a copy of the source:
extrn MessageBoxA: PROC
extrn ExitProcess: PROC
.data
mytit db 'The 64-bit world of Windows & assembler...', 0
mymsg db 'Hello World!', 0
.code
main proc
mov r9d, 0 ; uType = MB_OK
lea r8, mytit ; LPCSTR lpCaption
lea rdx, mymsg ; LPCSTR lpText
mov rcx, 0 ; hWnd = HWND_DESKTOP
call MessageBoxA
mov ecx, eax ; uExitCode = MessageBox(...)
call ExitProcess
main endp
End
Right now, I am just trying to get my 'first' x64 assembly program up and running so that I can start playing around and actually learn some assembly, so I just literally copied this source from here in an attempt to see if I could get anything to assemble correctly, but so far, no luck.
If I assemble this, I don't get any errors, neither during assembly-time nor run-time, but the program doesn't run as it's supposed to: it doesn't appear to do anything at all. Once the executable has been generated and I double-click on it, nothing happens, and if I go to the task manager, it doesn't seem to be running in the background either. What's going on?
I am using the default settings for MASM64 that are generated upon checking "masm" under "Build Customizations..." (found by right-clicking the project in the Solution Explorer) and changing the platform from Win32 to x64 in the Configuation Manager, the exceptions being that I've changed the "Entry Point" linker option to "main" and the "SubSystem" linker option to "Windows". (All of this is done in Visual Studio 2012.)
The debug info generated by running the program in Visual Studio is
'Hello World (ASM).exe' (Win32): Loaded 'D:\Google Drive\My Documents\Visual Studio
2012\Projects\Hello World (ASM)\x64\Release\Hello World (ASM).exe'. Symbols loaded.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\kernel32.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\KernelBase.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\user32.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\gdi32.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\imm32.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\msctf.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\msvcrt.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\nvinitx.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\advapi32.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\sechost.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\rpcrt4.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Program Files\NVIDIA Corporation\coprocmanager\detoured.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Program Files\NVIDIA Corporation\coprocmanager\Nvd3d9wrapx.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\setupapi.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\cfgmgr32.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\devobj.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Program Files\NVIDIA Corporation\coprocmanager\nvdxgiwrapx.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\PROGRA~1\NVIDIA~1\NVSTRE~1\rxinput.dll'. Module was built without symbols.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\ole32.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\oleaut32.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Loaded 'C:\Windows\System32\combase.dll'. Cannot find or open the PDB file.
'Hello World (ASM).exe' (Win32): Unloaded 'C:\PROGRA~1\NVIDIA~1\NVSTRE~1\rxinput.dll'
'Hello World (ASM).exe' (Win32): Unloaded 'C:\Windows\System32\combase.dll'
'Hello World (ASM).exe' (Win32): Unloaded 'C:\Windows\System32\oleaut32.dll'
'Hello World (ASM).exe' (Win32): Unloaded 'C:\Windows\System32\ole32.dll'
First-chance exception at 0x000007FA9A09B9FB (gdi32.dll) in Hello World (ASM).exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.
Unhandled exception at 0x000007FA9A09B9FB (gdi32.dll) in Hello World (ASM).exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.
First-chance exception at 0x000007FA9A09B9FB (gdi32.dll) in Hello World (ASM).exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.
Unhandled exception at 0x000007FA9A09B9FB (gdi32.dll) in Hello World (ASM).exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.
First-chance exception at 0x000007FA9A09B9FB (gdi32.dll) in Hello World (ASM).exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.
Unhandled exception at 0x000007FA9A09B9FB (gdi32.dll) in Hello World (ASM).exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.
The program '[1080] Hello World (ASM).exe' has exited with code 0 (0x0).

Before calling any of the WinAPI functions you must provide some space on the stack:
sub rsp,40
When calling other functions in x64 code on Windows you're required to provide shadow/spill/home space for that function, which is an area in which it can spill the 4 registers that are used for passing the first 4 parameters (ECX, EDX, R8, R9). Four quadwords amounts to 32 bytes (it's always 32 bytes, even if the function you call takes less than 4 arguments).
So why subtract 40 instead of 32?
There's also a requirement on stack alignment. Prior to calling a function you have to align the stack pointer to a multiple of 16 bytes (upon entering the function you'll also have RIPon the stack, making RSP % 16 == 8). So the subtraction of 8 extra bytes is because the stack pointer was 8 modulo 16 when the program started. Is that always the case? I don't know, but it seems plausible if whoever called your program's entrypoint (the OS or some runtime library) also aligned the stack before the call.
Instead of sub rsp,40 you could use:
and esp,0xFFFFFFF0 ; align
sub rsp,32 ; allocate shadow space

Related

Visual Studio 2019 shows "The program '[1456] regsvr32.exe' has exited with code 3 (0x3)" when I press "F5" and is not launching my Unreal Engine

At first I would like to say that recently I had my entire PC formatted. After that I installed both my Unreal Engine and Visual Studio 2019 at locations that were different from where they were before formatting.
At first I tried to open my project solution and tried building my solution with "F5". But it gave me an error The screenshot of my error. The error stated "Unable to start the program System cannot find the path specified". The path in that error message was the path that existed before formatting my PC.
Alternate link to the error screenshot: https://1drv.ms/u/s!AjZEJUZlPM7yizRT67cRETCHmIwY
Then I Uninstalled and reinstalled my UE4 and from there I launched my project and tried opening the Visual Studio files from the Editor. It did open the files, but the UE4 and the VS were not quite in sync. Some of the details that I hardcoded from VS through my codes were not quite showing up on my Unreal Editor.
I tried closing the UE4 and build my code again this time with F5. But this time The output log shows the line "Specified Path not found" for a temporary duration of time and then quickly it changes to this,
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\regsvr32.exe'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\kernel32.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\KernelBase.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\apphelp.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\AcLayers.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\msvcrt.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\user32.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\win32u.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\gdi32.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\gdi32full.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\msvcp_win.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbase.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\shlwapi.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\advapi32.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\sechost.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\rpcrt4.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\sfc.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\winspool.drv'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\sfc_os.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\imm32.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\combase.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\ole32.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\kernel.appcore.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\bcryptprimitives.dll'.
'regsvr32.exe' (Win32): Loaded 'C:\Windows\System32\uxtheme.dll'.
The thread 0xab4 has exited with code 3 (0x3).
The program '[17104] regsvr32.exe' has exited with code 3 (0x3).
Then I saw couple of fixes here in the stack overflow only, and I tried them out, these fixes are:
1. I went to Tools->Options->Projects and Solutions->Build and Run and I checked, under "On Run, when projects are out of date", the option was set to "Always Build" and under "On Run when build or deployment error occur", the option was set to "Prompt to launch". But nothing was launching and no prompt was showing too.
2. I searched for the exited with code 3 and there I found it said that it means the specific path file is not found and it can be fixed using ILMerge, so I searched ILMerge and from this website (https://www.inogic.com/blog/2018/06/automate-ilmerge-for-workflowsplugins-to-merge-multiple-assemblies-into-one-in-dynamics-365/) I found that Ill have to install ILMerge through the "Package Manager Console" in the "NutGet package manager". and I installed it using these two command lines, Install-Package ILMerge.MSBuild.Task and Install-Package ilmerge. Both of them showed successfully installed. But then I tried F5 again, but its the same.
3. I also went to Tools->Options->Debugging->General and at the very bottom, I checked the box for "Automatically close the console while debugging stops", which was unchecked by default.
4. At last I tried cleaning up my solution from the "Build" option and the I hit F5, this time the output that came was different and it showed that it had errors and it also prompted whether I want to launch the application or not. This is the output that I got,
1>------ Build started: Project: Alpha1, Configuration: Development_Editor x64 ------
1>Creating makefile for Alpha1Editor (no existing makefile)
1>Parsing headers for Alpha1Editor
1> Running UnrealHeaderTool "D:\AlphaGames\Alpha1\Alpha1.uproject" "D:\AlphaGames\Alpha1\Intermediate\Build\Win64\Alpha1Editor\Development\Alpha1Editor.uhtmanifest" -LogCmds="loginit warning, logexit warning, logdatabase error" -Unattended -WarningsAsErrors -abslog="C:\Users\USER\AppData\Local\UnrealBuildTool\Log_UHT.txt" -installed
1>Reflection code generated for Alpha1Editor in 7.5102243 seconds
1>Building Alpha1Editor...
1>Using Visual Studio 2019 14.26.28806 toolchain (C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.26.28801) and Windows 10.0.18362.0 SDK (C:\Program Files (x86)\Windows Kits\10).
1>Building 41 actions with 4 processes...
1> [1/41] Default.rc2
1> [2/41] SharedPCH.Engine.ShadowErrors.cpp
1> [3/41] ColliderMovementComponent.cpp
1>EXEC : error : Unable to rename D:\AlphaGames\Alpha1\Intermediate\Build\Win64\UE4Editor\Development\Alpha1\ColliderMovementComponent.cpp.txt.tmp to D:\AlphaGames\Alpha1\Intermediate\Build\Win64\UE4Editor\Development\Alpha1\ColliderMovementComponent.cpp.txt
1> [4/41] Collider.cpp
1> [5/41] Critter.cpp
1> [6/41] Enemy.cpp
1> [7/41] FloatingPlatform.cpp
1> [8/41] EnemyAnimInstance.cpp
1> [9/41] Weapon.cpp
1> [10/41] FloorSwitch.cpp
1> [11/41] MyActor.cpp
1>D:\AlphaGames\Alpha1\Source\Alpha1\MyActor.cpp(50): warning C4996: 'UPrimitiveComponent::AddTorque': Use AddTorqueInRadians instead. Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
1> [12/41] Item.cpp
1> [13/41] MainAnimInstance.cpp
1> [14/41] Pickup.cpp
1> [15/41] Main.cpp
1> [16/41] Alpha1GameModeBase.cpp
1> [17/41] Explosive.cpp
1> [18/41] Alpha1.cpp
1> [19/41] Alpha1.init.gen.cpp
1> [20/41] SpawnVolume.cpp
1> [21/41] Collider.gen.cpp
1> [22/41] Critter.gen.cpp
1> [23/41] ColliderMovementComponent.gen.cpp
1> [24/41] EnemyAnimInstance.gen.cpp
1> [25/41] Enemy.gen.cpp
1> [26/41] Explosive.gen.cpp
1> [27/41] FloatingPlatform.gen.cpp
1> [28/41] Alpha1GameModeBase.gen.cpp
1> [29/41] FloorSwitch.gen.cpp
1> [30/41] MainAnimInstance.gen.cpp
1> [31/41] Main.gen.cpp
1> [32/41] MyActor.gen.cpp
1> [33/41] Pickup.gen.cpp
1> [34/41] SpawnVolume.gen.cpp
1> [35/41] Weapon.gen.cpp
1>EXEC : error : Unable to rename D:\AlphaGames\Alpha1\Intermediate\Build\Win64\UE4Editor\Development\Alpha1\Weapon.gen.cpp.txt.tmp to D:\AlphaGames\Alpha1\Intermediate\Build\Win64\UE4Editor\Development\Alpha1\Weapon.gen.cpp.txt
1> [36/41] Alpha1_PlayerController.gen.cpp
1> [37/41] Item.gen.cpp
1> [38/41] Alpha1_PlayerController.cpp
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.MakeFile.Targets(46,5): error MSB3073: The command "chcp 65001 >NUL && D:\UE_4.25\UE_4.25\Engine\Build\BatchFiles\Build.bat Alpha1Editor Win64 Development -Project="D:\AlphaGames\Alpha1\Alpha1.uproject" -WaitMutex -FromMsBuild" exited with code 6.
1>Done building project "Alpha1.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
Please assist me with this issue. I am stuck with this problem for a long time. Tell me I f you want to know anything else or want me to share any other info about this issue. Let me know if you face issues in accessing the error screenshot link that I shared
Somebody from my team just had the exact same issue as what you described for your 4th fix attempt (the rename error). It appears to have been caused by their antivirus software, preventing the file mentioned in the error message to be renamed.
I'd advise you to completely disable the antivirus while you are building.
I've read similar errors can also be caused by special characters in the file path, or the path being too long (over 260).

PDB symbol for clr.dll not loaded

I get following message when I execute "!name2ee app.exe!Program".How can I fix that?
I am using VS2013.
.load sos
extension C:\Windows\Microsoft.NET\Framework\v4.0.30319\sos.dll loaded
!name2ee app.exe!Program
PDB symbol for clr.dll not loaded
Make sure you have an Internet connection
Set "Microsoft Symbol Servers" in Options / Debugging / Symbols

Visual Studio error: The program '[5308] myNewOpenCV.exe' has exited with code -1073741701 (0xc000007b)

I was following this tutorial and tried to run the following code:
#include <opencv\cv.h>
#include <opencv\highgui.h>
using namespace cv;
int main() {
//Create matric to store image
Mat image;
//initialize capture
VideoCapture cap;
cap.open(0);
//create window to show image
namedWindow("window", 1);
while (1){
// copy webcam stream to image
cap >> image;
// print image to screen
imshow("window", image);
//delay 33ms
waitKey(33);
}
}
However I got the following errors:
'myNewOpenCV.exe' (Win32): Loaded 'C:\Users\Or\Copy\Documents\Visual Studio 2013\Projects\myNewOpenCV\Debug\myNewOpenCV.exe'. Symbols loaded.
'myNewOpenCV.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Cannot find or open the PDB file.
'myNewOpenCV.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Cannot find or open the PDB file.
'myNewOpenCV.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Cannot find or open the PDB file.
The program '[5308] myNewOpenCV.exe' has exited with code -1073741701 (0xc000007b).
and the program does not run. I've tried to re install the opevCV libraries like suggested on some places but it didn't work.
I'm running Visual Studio 2013 Version 12.0.21005.1 REL and Windows 7 64-bit

How to disassembly my driver?

I am trying kernel debugging using vmware and windbg.I have connected two OS and all symbols are loaded successfully.If I want to see my driver in memory how can I disassembly that?
I have tried lm commands and lmvm commands
kd> lmvm comint32
start end module name
88da9000 88daf000 comint32 (private pdb symbols) C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\comint32.pdb\653387D894B4412FA9E30659E58DD47C1\comint32.pdb
Loaded symbol image file: comint32.sys
Image path: \SystemRoot\System32\Drivers\comint32.sys
Image name: comint32.sys
Timestamp: Thu Apr 11 20:10:55 2013 (51677B3F)
CheckSum: 0000CACF
ImageSize: 00006000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
x comint32!* should dump all the symbols of the module along with their addresses in memory.
You can then either use the u command (with the name (e.g. comint32!DriverEntry) or the address of a function as a parameter) to disassemble into the main window or you can open the disassembly window and paste the name/address into it and browse the disassembled code there.
See your windbg reference for further details.

Qt 4.8.2 QString toStdString unhandled exception

void QuinielaApuesta::funcion(QString & str)
{
std::string cadenita = str.toStdString();
std::cout << cadenita << std::endl;
}
I am on Qt 4.8.2 for VS2010, Windows 7 N 64-bit, Visual Studio 2010 and using the QString method "toStdString()" (or something somewhat related) causes an Unhandled exception.
it doesn't matter where I use the line
std::string cadenita = str.toStdString();
It will cause an unhandled exception. In this particular case, it happens right after I get out of the method "funcion"s scope. But it happens in the current context of the scope escape (That is, if you put this line in an object's constructor, it will proceed as expected until the end of the constructor, and then when it should proceed to a higher scope level, it will send an Unhandled Exception error).
I have isolated the issue to .toStdString by trial and error, and I cannot say if other methods might (or might) have this same issue. I can say, however, that as soon as the line is commented, it all works ok. In fact, if I replace said line with a simple
std::cout << "Some Funny Test Text" std::endl;
It all works fine and dandy.
The error is
Unhandled exception at 0x53b8ad7a (msvcp100d.dll) in C_plus_plus_QT_project.exe: 0xC0000005: Access violation reading location 0xccccccd0.
And then in file xutility, line 201
#if _ITERATOR_DEBUG_LEVEL == 2
if (_Myproxy != 0)
{ // proxy allocated, drain it
_Lockit _Lock(_LOCK_DEBUG);
for (_Iterator_base12 **_Pnext = &_Myproxy->_Myfirstiter;
*_Pnext != 0; *_Pnext = (*_Pnext)->_Mynextiter) // HERE IS THE LINE WHERE THE BREAK KICKS IN
(*_Pnext)->_Myproxy = 0;
_Myproxy->_Myfirstiter = 0;
}
Visual Studio's output is:
'C_plus_plus_QT_project.exe': Loaded 'C:\Users\aravasio\Desktop\C_plus_plus_QT_project\Debug\C_plus_plus_QT_project.exe', Symbols loaded.
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\ntdll.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\kernel32.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\KernelBase.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Users\aravasio\Desktop\C_plus_plus_QT_project\Debug\QtGui4.dll', Binary was not built with debug information.
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\gdi32.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\user32.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\advapi32.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\msvcrt.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\sechost.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\rpcrt4.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\sspicli.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\cryptbase.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\lpk.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\usp10.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\comdlg32.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\shlwapi.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\comctl32.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\shell32.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\oleaut32.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\ole32.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\imm32.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\msctf.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\winmm.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\winspool.drv', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Users\aravasio\Desktop\C_plus_plus_QT_project\Debug\QtCore4.dll', Binary was not built with debug information.
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\ws2_32.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\nsi.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcp90.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\msvcp100d.dll', Symbols loaded.
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\msvcr100d.dll', Symbols loaded.
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\uxtheme.dll', Cannot find or open the PDB file
'C_plus_plus_QT_project.exe': Loaded 'C:\Windows\SysWOW64\dwmapi.dll', Cannot find or open the PDB file
First-chance exception at 0x53b8ad7a (msvcp100d.dll) in C_plus_plus_QT_project.exe: 0xC0000005: Access violation reading location 0xccccccd0.
Unhandled exception at 0x53b8ad7a (msvcp100d.dll) in C_plus_plus_QT_project.exe: 0xC0000005: Access violation reading location 0xccccccd0.
If I can provide any other information about my system, I will be glad to.
I can only make some sort of educated guess that this is not a Qt bug, because at home I am having no problem at all (but at home I am using an x86 W7, so it might not be a good example).
Does anybody know about this? I've googled quite a bit, but every error seems to have been addressed in an old hotfix.
Should I just abandon ship and try VS2008? Does it work with x64 environments? (Release is going to be for x86, btw, not x64)
You compiled the debug target but you linked it with the release variants of the Qt dlls (QtCore4.dll and QtGui4.dll instead of QtCored4.dll and QtGuid4.dll).

Resources