?? loaded_dlls.shtml.htm
字號(hào):
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!-- saved from url=(0060)http://go1.163.com/~81000/source/debug/loaded_dlls.shtml.htm -->
<HTML><HEAD><TITLE>mfc programmer's sourcebook : debugging tips</TITLE>
<META content="text/html; charset=iso-8859-1" http-equiv=content-type>
<META content="zafir anjum" name=author>
<META content="source codes for debugging" name=description>
<META content="source code debug" name=keywords>
<META content="MSHTML 5.00.2614.3500" name=GENERATOR></HEAD>
<BODY background=loaded_dlls.shtml.files/di2001.jpg bgColor=#ffffff
tppabs="http://www.codeguru.com/fancyhome/back.gif">
<H3 align=center><FONT color=#a0a099><!-- article title -->check for loaded dlls
</FONT></H3>
<HR>
<!-- author and contact details -->
<P>this article was contributed by <!-- author email --><A
href="mailto:shyamss@technologist.com"><!-- author name -->shyam sundaram</A>. <!-- text / source code --></P>
<P><!-- the 'p' starts a paragraph of normal text -->hi , i wanted to pass on
one of the methods that has helped in the past, in debugging client server
applications, in which you may have several version of your dll. making use of
small utilities like wps/killer/nuke in determing the dll that is lodaed at run
time. this helps you to sometimes sort of understand in which portion of your
application, a problem occurs. </P>
<P>this becomes really useful when you distribute your software to users not
necessarily in the same location and on diverse platforms (w3.1,w95, nt and so
on). sometimes a dump of the active dll's helps you nail down the problem. <!-- posted / update date mm/dd/yy - add to the list --></P>
<P>date posted: <!-- date here -->17 may 1998 </P></BODY></HTML>
?? 快捷鍵說明
復(fù)制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號(hào)
Ctrl + =
減小字號(hào)
Ctrl + -