用MFC開發的應用軟體，發生崩潰。
系統事件記錄資訊如下：
錯誤模塊名稱：MFC42U.DLL，版本：6.6.8063.0，時間戳：0x4ce7b886
例外代碼：0xc0000005
錯誤偏移量：0x0001c62b
Dump檔案分析結果如下：
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for cufft32_50_35.dll -
GetUrlPageData2 (WinHttp) failed: 12002.
DUMP_CLASS: 2
DUMP_QUALIFIER: 400
FAULTING_IP:
ntdll!_RtlUserThreadStart+1b
774037c8 cc int 3
EXCEPTION_RECORD: 0012f840 -- (.exr 0x12f840)
ExceptionAddress: 719987b1 (mfc42u!AfxWndProc+0x00000029)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 025d2d60
Attempt to read from address 025d2d60
FAULTING_THREAD: 000015f0
DEFAULT_BUCKET_ID: STATUS_BREAKPOINT
PROCESS_NAME: GUIMgr.exe
ERROR_CODE: (NTSTATUS) 0x80000003 - {
EXCEPTION_CODE: (NTSTATUS) 0x80000003 (2147483651) - {
EXCEPTION_CODE_STR: 80000003
WATSON_BKT_PROCSTAMP: 58c751e1
WATSON_BKT_PROCVER: 1.0.0.15
PROCESS_VER_PRODUCT: NMS NeuVision DR III
WATSON_BKT_MODULE: unknown
WATSON_BKT_MODVER: 0.0.0.0
WATSON_BKT_MODOFFSET: 0
WATSON_BKT_MODSTAMP: bbbbbbb4
BUILD_VERSION_STRING: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
MODLIST_WITH_TSCHKSUM_HASH: 620ccc7cdf1d9f13d868b9362fcef46eed6749b9
MODLIST_SHA1_HASH: a1a579dab9f6da6e7c84d652ed200dad749e5514
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
PRODUCT_TYPE: 1
SUITE_MASK: 336
DUMP_FLAGS: c07
DUMP_TYPE: 0
ANALYSIS_SESSION_HOST: DESKTOP-QFIDE1T
ANALYSIS_SESSION_TIME: 03-16-2017 19:52:37.0875
ANALYSIS_VERSION: 10.0.14321.1024 x86fre
CONTEXT: 0012f85c -- (.cxr 0x12f85c)
eax=025d2d40 ebx=00000000 ecx=02583730 edx=29c6ce80 esi=000313ae edi=0000001c
eip=774037c8 esp=0012ffdc ebp=0012ffec iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202
ntdll!_RtlUserThreadStart+0x1b:
774037c8 cc int 3
Resetting default scope
FOLLOWUP_IP:
ntdll!_RtlUserThreadStart+1b
774037c8 cc int 3
READ_ADDRESS: 025d2d60
BUGCHECK_STR: STATUS_BREAKPOINT
THREAD_ATTRIBUTES:
OS_LOCALE: CHS
PROBLEM_CLASSES:
Tid [0x0]
Frame [0x00]
String [STATUS_BREAKPOINT]
Data Bucketing
LAST_CONTROL_TRANSFER: from 00000000 to 774037c8
STACK_TEXT:
0012ffec 00000000 0046ad28 7ffd3000 00000000 ntdll!_RtlUserThreadStart+0x1b
STACK_COMMAND: .cxr 12f85c ; kb ; .cxr 0x12f85c ; kb
THREAD_SHA1_HASH_MOD_FUNC: 7c988acdf3188b3f594f31262124174034535dde
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2834fec2684cd8d8c7cc308113bb72d56c37d2f2
THREAD_SHA1_HASH_MOD: 4d6a592812b1f521b481ecb6f54e3789559d0477
FAULT_INSTR_CODE: 909090cc
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ntdll!_RtlUserThreadStart+1b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ntdll
IMAGE_NAME: ntdll.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7b96e
BUCKET_ID: STATUS_BREAKPOINT_ntdll!_RtlUserThreadStart+1b
PRIMARY_PROBLEM_CLASS: STATUS_BREAKPOINT_ntdll!_RtlUserThreadStart+1b
FAILURE_EXCEPTION_CODE: 80000003
FAILURE_IMAGE_NAME: ntdll.dll
BUCKET_ID_IMAGE_STR: ntdll.dll
FAILURE_MODULE_NAME: ntdll
BUCKET_ID_MODULE_STR: ntdll
FAILURE_FUNCTION_NAME: _RtlUserThreadStart
BUCKET_ID_FUNCTION_STR: _RtlUserThreadStart
BUCKET_ID_OFFSET: 1b
BUCKET_ID_MODTIMEDATESTAMP: 4ce7b96e
BUCKET_ID_MODCHECKSUM: 1490d9
BUCKET_ID_MODVER_STR: 6.1.7601.17514
BUCKET_ID_PREFIX_STR: STATUS_BREAKPOINT_
FAILURE_PROBLEM_CLASS: STATUS_BREAKPOINT
FAILURE_SYMBOL_NAME: ntdll.dll!_RtlUserThreadStart
FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_ntdll.dll!_RtlUserThreadStart
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/GUIMgr.exe/1.0.0.15/58c751e1/unknown/0.0.0.0/bbbbbbb4/80000003/00000000.htm?Retriage=1
TARGET_TIME: 2017-03-15T06:05:18.000Z
OSBUILD: 7601
OSSERVICEPACK: 17514
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
OSPLATFORM_TYPE: x86
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) EmbeddedNT SingleUserTS
USER_LCID: 0
OSBUILD_TIMESTAMP: 2010-11-20 20:02:55
BUILDDATESTAMP_STR: 101119-1850
BUILDLAB_STR: win7sp1_rtm
BUILDOSVER_STR: 6.1.7601.17514
ANALYSIS_SESSION_ELAPSED_TIME: 9b67
ANALYSIS_SOURCE: UM
FAILURE_ID_HASH_STRING: um:status_breakpoint_80000003_ntdll.dll!_rtluserthreadstart
FAILURE_ID_HASH: {a1fc1684-bea8-193f-aedf-2b02aa4571a3}
Followup: MachineOwner
---------
uj5u.com熱心網友回復：
主要是訪問了空指標等。uj5u.com熱心網友回復：
除錯模式 加斷點 出錯的地方在左下角呼叫堆疊里面 挨個點擊 直到看懂的那行代碼 就是你出錯的地方了uj5u.com熱心網友回復：
崩潰的時候在彈出的對話框按相應按鈕進入除錯，按Alt+7鍵查看Call Stack即“呼叫堆疊”里面從上到下列出的對應從里層到外層的函式呼叫歷史。雙擊某一行可將游標定位到此次呼叫的源代碼或匯編指令處，看不懂時雙擊下一行，直到能看懂為止。轉載請註明出處，本文鏈接：https://www.uj5u.com/gongcheng/106604.html
標籤：界面
上一篇：xp系統下使用win7生成的軟體無法讀取電流，串口有不同嗎？
下一篇：專案微管理40 - 第一