Could you pls tell me if there is something wrong in the following output....(Debug)



  • I installed qt-vs-addin-1.1.10 in Visual Studio 2010, following this tutorial "Setup Qt for VS2010":http://www.pansenti.com/wordpress/?page_id=286

    I tried to make and build a simple widget, and I guess everything is fine, but I don't understand why if you check the output from debug (below) there are various issues....

    • I did something wrong or is nothing to worry about?

    Pls help ;)

    ---------------------------------------------------------------------------Output from build:
    1> Deleting file "Debug\test1.unsuccessfulbuild".
    1> Touching "Debug\test1.lastbuildstate".
    1>
    1>Build succeeded.
    1>
    1>Time Elapsed 00:00:03.92
    ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

    ------------------------------------------------------------------------------Output from Build Order:

    1>------ Build started: Project: test1, Configuration: Debug Win32 ------
    1>Build started 10/05/2012 14:16:21.
    1>InitializeBuildStatus:
    1> Creating "Debug\test1.unsuccessfulbuild" because "AlwaysCreate" was specified.
    1>CustomBuild:
    1> Moc'ing test1.h...
    1>ClCompile:
    1> moc_test1.cpp
    1> main.cpp
    1> test1.cpp
    1> Generating Code...
    1> All outputs are up-to-date.
    1>Link:
    1> LINK : C:\Users\Fab\Desktop\C++\QT 4\test1\test1.exe not found or not built by the last incremental link; performing full link
    1> test1.vcxproj -> C:\Users\Fab\Desktop\C++\QT 4\test1\test1.exe
    1>FinalizeBuildStatus:
    1> Deleting file "Debug\test1.unsuccessfulbuild".
    1> Touching "Debug\test1.lastbuildstate".
    1>
    1>Build succeeded.
    1>
    1>Time Elapsed 00:00:03.92
    ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

    -----------------------------------------------------------------------------------Output from Debug:

    'test1.exe': Loaded 'C:\Users\Fab\Desktop\C++\QT 4\test1\test1.exe', Symbols loaded.
    'test1.exe': Loaded 'C:\Windows\SysWOW64\ntdll.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\kernel32.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\KernelBase.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Qt\4.8.1\bin\QtCored4.dll', Symbols loaded.
    'test1.exe': Loaded 'C:\Windows\SysWOW64\user32.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\gdi32.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\lpk.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\usp10.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\msvcrt.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\advapi32.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\sechost.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\rpcrt4.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\sspicli.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\cryptbase.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\ole32.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\ws2_32.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\nsi.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\msvcp100d.dll', Symbols loaded.
    'test1.exe': Loaded 'C:\Windows\SysWOW64\msvcr100d.dll', Symbols loaded.
    'test1.exe': Loaded 'C:\Qt\4.8.1\bin\QtGuid4.dll', Symbols loaded.
    'test1.exe': Loaded 'C:\Windows\SysWOW64\comdlg32.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\shlwapi.dll', Cannot find or open the PDB file
    'test1.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
    'test1.exe': Loaded 'C:\Windows\SysWOW64\shell32.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\oleaut32.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\imm32.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\msctf.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\winmm.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\winspool.drv', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\nvinit.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\uxtheme.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\dwmapi.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\cryptsp.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\rsaenh.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\RpcRtRemote.dll', Cannot find or open the PDB file
    'test1.exe': Loaded 'C:\Windows\SysWOW64\clbcatq.dll', Cannot find or open the PDB file
    The thread 'Win32 Thread' (0x1290) has exited with code 0 (0x0).
    The thread 'Win32 Thread' (0xbac) has exited with code 0 (0x0).
    The thread 'Win32 Thread' (0x1b6c) has exited with code 0 (0x0).
    The thread 'Win32 Thread' (0xf00) has exited with code 0 (0x0).
    The program '[3648] test1.exe: Native' has exited with code 0 (0x0).


  • Moderators

    There is nothing to worry about.
    The build output are showing that you succeeded with building.
    The output from your debug run provides information about the different dlls are loaded. Those are system dlls and you do not have much influence on them. The pdb files are program databases and those are not existing for users to my understanding. They are keeping debug information and your compiler will them for your libs/dlls/exes when build. Then they are used during debugging.



  • Thanks for your reply! ;)


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.