T錛氳璇撮氳繃WAP鎺ュ叆鐐硅繛鎺ヤ竴涓湇鍔″櫒鐨勮繃紼嬨?
W錛氬垵濮嬪寲WinSock搴擄紞璋冪敤socket()鍒涘緩涓涓猻ocket,璋冪敤connect榪炴帴10.0.0.172鏈嶅姟鍣紝鐒跺悗鍙戦佷竴涓狢ONNECT璇鋒眰榪炴帴鐩爣鏈嶅姟鍣?..(琚墦鏂?.
闃呰鍏ㄦ枃
]]>
Artistic Style is a reindenter and reformatter of C, C++, C# and Java source code.
autoconf
Development version of the automatic configure script builder.
automake
A tool for generating GNU-compliant Makefiles.
bashdb
Debugger for bash scripts
cppcheck
A tool for static C/C++ code analysis
doxygen
A documentation system for C++, C, Java, Objective-C, IDL and to some extent PHP, C# and D.
gcc-tools-autoconf
automatic configure script builder
gcc-tools-automake
a tool for generation GNU-compliant Makefiles.
git
Fast Version Control System
glib-devel
Gnome C function library
indent
C/C++ language source code formatting program
libiconv
GNU character set conversion library and utilities.
libjpeg-devel
A library for manipulationg JPEG image format files.
libpng
PNG library.
pcre-devel
Perl-Compatible Regular Expressions.
]]>
porting mupdf to Windows.
It helps to know that there鈥檚 at least one reason for a changed behavior under
the debugger: it automatically triggers using debugging heap. While debugging
heap usually helps find problems, sometimes it does the opposite by changing
the details of memory allocation.
One helpful tool when debugging memory problems on Windows is gflags which can
enable page heap instrumentation for a given program. It works by putting each
allocation into a separate region of memory and putting a non-readable page
right after that. Also, upon freeing it makes the memory unreadable. That way
an overwrite of memory block while it鈥檚 still being used or accessing the
memory after it was freed will cause immediate crash.
The downside is that using gflags uses much more memory. But in those days of
cheap gigabytes it鈥檚 not a problem that can鈥檛 be solved with a couple hundred
bucks.
Basic usage of gflags.exe is simple: gflags /p /full /enable foo.exe
From now on foo.exe will always be run with this instrumentation turned on. To
disable, do gflags /p /disable foo.exe
To see which programs have page heap enabled, do gflags /p. gflags offers many
other option and you can learn about them via gflags /?. If you run gflags
without any options, you鈥檒l get a (very confusing) GUI.
It worked like a charm. I got a crash on accessing freed memory and all I had
to do was to backtrack to where this memory was allocated to figure out the
problem.
reference: http://blog.kowalczyk.info/article/gflags-a-debugging-story.html
]]>
聽
鍒嗘瀽錛氬洜涓簂og4cpp鍦ㄧ敓鎴怤TEventLogAppender.dll鏃訛紝闇瑕佽繛鎺TEventLogCategories.mc鏂囦歡銆傛墍浠ワ紝欏圭洰璁劇疆浜嗚嚜瀹氫箟鐨勭敓鎴愭楠ゅ幓鐢熸垚NTEventLogAppender.dll銆備絾浠巚c6鐨勫伐紼嬫枃浠惰漿鎹㈡椂錛岃繖浜涙楠ゅ嵈娌℃湁姝ｇ‘鐨勮漿鎹㈣繃鏉ャ備粠鑰屽嚭鐜頒笂榪伴棶棰樸?/p>
瑙ｅ喅鏂規(guī)硶錛氶噸鏂板～鍐機(jī)ustom Build Step欏廣?/p>
鍏朵腑錛孋ommandLine濉啓浠ヤ笅鍐呭錛?/p>
if not exist $(OutDir) md $(OutDir)
"mc.exe" -h $(OutDir) -r $(OutDir) $(SolutionDir)NTEventLogCategories.mc
"RC.exe" -r -fo $(OutDir)\$(InputName).res $(ProjectDir)\$(InputName).rc
"link.exe" /MACHINE:IX86 -dll -noentry -out:$(OutDir)\NTEventLogAppender.dll $(OutDir)\$(InputName).res
Outputs濉啓錛?(OutDir)\NTEventLogAppender.dll
閫傜敤鑼冨洿錛歭og4cpp欏圭洰銆乴og4cppDLL欏圭洰鐨凞ebug鍜孯elease閰嶇疆銆傚悓鏃訛紝璇ユ柟娉曢傜敤浜巚s2003(vc7.1)銆?/p>
]]>
濡傛灉鎴戜滑灝?/span> 0x1234abcd 鍐欏叆鍒頒互 0x0000 寮濮嬬殑鍐呭瓨涓紝鍒欑粨鏋滀負(fù):
聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽聽 big-endian 聽聽little-endian
0x0000聽聽聽聽聽聽聽聽聽 0x12聽聽聽聽聽聽聽聽聽聽聽 0xcd
0x0001聽聽聽聽聽聽聽聽聽 0x34聽聽聽聽聽聽聽聽聽聽聽 0xab
0x0002 聽聽聽聽聽聽聽聽 0xab聽聽聽聽聽聽聽聽聽聽聽 0x34
0x0003聽聽聽聽聽聽聽聽聽 0xcd聽聽聽聽聽聽聽聽聽聽聽聽0x12
]]>
Download錛歨ttp://sourceforge.net/projects/tinyxml 闃呰鍏ㄦ枃
]]>