PROJECT 'K: July 2008

Sunday, July 27, 2008

[Visual C++ 6.0] Parsing error : Quoted String Expected.....

On Visual Studio 6.0, after added active x control on dialog, maybe class wizzard will be failed.
Shown following message box.

I guess , this error caused by visual C++ parser can't parsing '<' and '>' character.
On Dialog box's header files, you can see following lines.

//{{AFX_INCLUDES()
#include <ninumedit.h>
//}}AFX_INCLUDES

Correct '<' and '>' character to ' " '.

//{{AFX_INCLUDES()
#include "NiNumedit.h"
//}}AFX_INCLUDES

Thursday, July 17, 2008

A LNK2005 error occurs

A LNK2005 error occurs when the CRT library and MFC libraries are linked in the wrong order in Visual C++
View products that this article applies to.
function loadTOCNode(){}
Article ID:148652
Last Review:March 13, 2008
Revision:7.0
This article was previously published under Q148652
On This Page
SYMPTOMS
CAUSE
RESOLUTION
Solution One: Force Linker to Link Libraries in Correct Order
Solution Two: Locate and Correct the Problem Module
STATUS
MORE INFORMATION
Steps to Reproduce the Problem in Visual C++ .NET
SYMPTOMS

When the C Run-Time (CRT) library and Microsoft Foundation Class (MFC) libraries are linked in the wrong order, you may receive one of the following LNK2005 errors:
nafxcwd.lib(afxmem.obj) : error LNK2005:"void * __cdecl operator new(unsigned int)"(??2@YAPAXI@Z) alreadydefined in LIBCMTD.lib(new.obj)
nafxcwd.lib(afxmem.obj) : error LNK2005:"void __cdecl operator delete(void *)"(??3@YAXPAX@Z) already definedin LIBCMTD.lib(dbgnew.obj)
nafxcwd.lib(afxmem.obj) : error LNK2005:"void * __cdecl operator new(unsigned int,int,char const *,int)"(??2@YAPAXIHPBDH@Z) already defined in LIBCMTD.lib(dbgnew.obj)
mfcs40d.lib(dllmodul.obj): error LNK2005: _DllMain@12 already defined inMSVCRTD.LIB (dllmain.obj)
mfcs42d.lib(dllmodul.obj): error LNK2005: _DllMain@12 already defined inmsvcrtd.lib(dllmain.obj)
Back to the top
CAUSE
The CRT libraries use weak external linkage for the new, delete, and DllMain functions. The MFC libraries also contain new, delete, and DllMain functions. These functions require the MFC libraries to be linked before the CRT library is linked.
Back to the top
RESOLUTION
loadTOCNode(1, 'resolution');
There are two ways to resolve this problem. The first solution involves forcing the linker to link the libraries in the correct order. The second solution allows you to find the module that is causing the problem and to correct it. Note The following steps are based on Visual C++ 6.0.
Back to the top
Solution One: Force Linker to Link Libraries in Correct Order
loadTOCNode(2, 'resolution');
1. On the Project menu, click Settings.
2. In the Settings For view of the Project Settings dialog box, click to select the project configuration that is getting the link errors.
3. On the Link tab, click to select Input in the Category combo box.
4. In the Ignore libraries box, insert the library names (for example, Nafxcwd.lib;Libcmtd.lib). Note The linker command-line equivalent in /NOD:.
5. In the Object/library modules box, insert the library names. You must make sure that these are listed in order and as the first two libraries in the line (for example, Nafxcwd.lib Libcmtd.lib).To set this option in Visual C++ .NET, read the "Setting Visual C++ Project Properties" online help topic.
Back to the top
Solution Two: Locate and Correct the Problem Module
To view the current library link order, follow these steps:
1. On the Project menu, click Settings.
2. In the Settings For view of the Project Settings dialog box, click to select the project configuration that is getting the link errors.
3. On the Link tab, type /verbose:lib in the Project Options box.
4. Rebuild your project. The libraries will be listed in the output window during the linking process.
Back to the top
STATUS
This behavior is by design.
Back to the top
MORE INFORMATION
When you use the MFC libraries, you must make sure that they are linked before the CRT library is linked. You can do this by making sure that every file in your project includes Msdev\Mfc\Include\Afx.h first, either directly (#include ) or indirectly (#include ). The Afx.h include file forces the correct order of the libraries, by using the #pragma comment (lib,"") directive. If the source file has a .c extension, or the file has a .cpp extension but does not use MFC, you can create and include a small header file (Forcelib.h) at the top of the module. This new header makes sure that thelibrary search order is correct. Visual C++ does not contain this header file. To create this file, follow these steps:
1. Open Msdev\Mfc\Include\Afx.h.
2. Select the lines between #ifndef _AFX_NOFORCE_LIBS and #endif //!_AFX_NOFORCE_LIBS.
3. Copy the selection to the Windows Clipboard.
4. Create a new text file.
5. Paste the contents of the Clipboard into this new file.
6. Save the file as Msdev\Mfc\Include\Forcelib.h.
Back to the top
Steps to Reproduce the Problem in Visual C++ .NET
1. Start Microsoft Visual Studio .NET.
2. On the File menu, point to New, and then click Project.
3. Click Visual C++ Projects under Project Types, and then click MFC Application under Templates.
4. In the Name text box, type Q148652.
5. In the Location text box, type C:\Test, and then click OK.
6. In the MFC Application Wizard dialog box, click Application Type.
7. Click Dialog based under Application type, and then click Use MFC in a static library under Use of MFC.
8. Click Finish.
9. In Solution Explorer, under Source Files select all the three .cpp files.
10. Right-click the three selected files, and then click Remove.
11. Right-click Source files, point to Add, and then click Add New Item.
12. Click C++ files under Templates. In the Name text box, type Aa. Click Open.
13. Paste the following code in the Aa.cpp file: int test(){new int; return 1;}
14. Right-click Source Files, point to Add, and then click Add Existing Item.
15. Select the following files:
• Q148652.cpp
• Q148652Dlg.cpp
• stdafx.cpp
16. Click Open.
17. The files that you selected in step 15 appear under Source Files.
18. Select all four .cpp files under Source Files.
19. Right-click the four .cpp files that you selected, and then click Properties.
20. Expand Configuration Properties, and then expand C/C++.
21. Click Precompiled Headers.
22. Set the Create/Use Precompiled Header property to Not Using Precompiled Headers. Click OK.
23. On the Build menu, click Rebuild Solution.
Back to the top

APPLIES TO
• Microsoft Visual C++ 2008 Express Edition
• Microsoft Visual C++ 4.0 Standard Edition
• Microsoft Visual C++ 4.1 Subscription
• Microsoft Visual C++ 5.0 Enterprise Edition
• Microsoft Visual C++ 6.0 Enterprise Edition
• Microsoft Visual C++ 5.0 Professional Edition
• Microsoft Visual C++ 6.0 Professional Edition
• Microsoft Visual C++, 32-bit Learning Edition 6.0
• Microsoft Visual C++ .NET 2002 Standard Edition
• Microsoft Visual C++ .NET 2003 Standard Edition

Origin Page : http://support.microsoft.com/kb/148652

Monday, July 14, 2008

Debugging with WinDBG

Debug with WinDBG
WinDBG is a powerful debugging tool for Microsoft Windows.
You can debugging with Visual Studio, but you can’t install a Visual Studio to every target machines.
WinDBG is light and easy to debugging so that it can be find bug easily.

1. Install WinDBG .
Installing a latest Platform SDK on your computer, WinDBG will be installed by default.
But WinDBG can be update latest version.
So on this page, I recommend install latest version
You can download following page.
WinDBG Download :
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

2. Install Symbol package.
Symbol files has debugging informations. Like a registry status or function address.
We can debugging program that we’ve programmed codes with *.pdb files. Also We need system dll’s *.pdb files for debugging correctly.
Bunch of system dll’s debugging information files are symbol package.
You can download following page.
Symbol File Download :
http://www.microsoft.com/whdc/DevTools/Debugging/symbolpkg.mspx

3. WinDBG Setting.
After install a WinDBG, setting an environment for WinDBG.
On registry editor (regedit.exe), add new registry key “WinDBG” on
HKLM\Software\Microsoft\Windows\CurrentVersion\App Path\

Then change a default value to "WinDBG.exe" Installed directory.

That can make a start WinDBG , entering a “WinDBG” keyword on “Run” without entering a full path.
Next, add(or modify) a environment variable that symbol file path and symbol server.
On Control Panel>>System>>Advanced>>Environment Variables,
Add(or modify) “_NT_SYMBOL_PATH” value to
“srv*c:\Symbols*http://msdl.microsoft.com/download/symbols” .
Entering an “WinDBG –I” on “Run…” , WinDBG is became a postmortem debugger.
(You can change postmortem debugger to Visual Studio, check items on Visual Studio>>Tools>>Options>>Debugging>>Just-In-Time tab)
Start Debugging.
Now I’ll show debugging with WinDBG using program that occurring an error.
I’ve create a SDI Application project and added following codes on
CWinDBGTestApp::InitInstance() function.

TCHAR p[5] = {0,};
TCHAR* txt = _T("Memory Overrun");
CopyMemory(p,txt, _tcslen(txt)*sizeof(TCHAR)); //Actually should be
// occurre an error this line.
//Visual C++ 6 does not. So I added following line.
delete txt;

Executing a program, following error box will be shown.

Pressing a “Retry” button , WinDBG will execute.
WinDBG printed loaded modules and registry values.
For more specific results, re-setting a symbol path with following command.
(You do not need to doing this every time.)
.sympath cache… has WinDBG response time to do update new symbol files faster.
After this, re-load symbols with .reload command.

And print stack back traces with “K*” command.
On this page, we can find which line makes an error using “kb” command.

We can notify that there is some problem on 97th line on "WinDBGTest.cpp".

TCHAR p[5] = {0,};
TCHAR* txt = _T("Memory Overrun");
CopyMemory(p,txt, _tcslen(txt)*sizeof(TCHAR)); //This line is also wrong code
delete txt; //97th line

This sample shown an error on “delete txt” line on VC++6. On Visual Studio 2005(or upper) , occure an error on CopyMemory(…) Line. If you want to know more specific information, read a WinDBG manual on ("% WinDBG Installed %\debugger.chm”) or msdn page.

**Referenced data

http://msdn.microsoft.com/en-us/library/cc266370.aspx
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
WinDBG manual.
Debugging Applications for Microsoft .NET and Microsoft Windows
-MS Press-
Advanced Windows Debugging
-Addison Wesley-