谁能帮我看一下WinDbg的分析结果是什么意思?

tsinghua605 2009-06-04 12:50:42
我运行了自己编写的exe程序,结果出错,然后我就用WinDbg Attach to这个出错的程序上,又用!analyze -v命令分析了一下,但是看不明白怎么回事?第一次用Windbg,不知道如何使用,也请各位介绍一下想用好WinDbg需要从哪里入手?谢谢!
...全文
1817 13 打赏 收藏 转发到动态 举报
写回复
用AI写文章
13 条回复
切换为时间正序
请发表友善的回复…
发表回复
shifters 2011-09-21
  • 打赏
  • 举报
回复
首先要正确设置windbg的符号文件,源码路径等,这个看教程就可以了。可以设置通过windbg直接启动调试程序,用命令行,使用-g参数可以越过初始化断点。如果windbg设置正确的话,当程序崩溃时能够定位到出错的代码行,即使找不到具体的代码行,出错时的内存与寄存器值也会被保存,应该可以分析出错误的
dong4464he 2011-03-24
  • 打赏
  • 举报
回复
哪位大侠能讲解一下这个工具的使用方法呢?
lee_weidong 2009-08-13
  • 打赏
  • 举报
回复
配置错误
LiuYinChina 2009-06-05
  • 打赏
  • 举报
回复
ip_sctp?我这边可以没有运行的环境,
用日志吧!
LiuYinChina 2009-06-05
  • 打赏
  • 举报
回复
EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 7c81a3e1 (ntdll!DbgBreakPoint)
ExceptionCode: 80000003 (Break instruction exception)

??你运行的是 Debug 版的,是吗?
LiuYinChina 2009-06-05
  • 打赏
  • 举报
回复
方便给代码吗?我来试一下,
LiuYinChina 2009-06-04
  • 打赏
  • 举报
回复
你用 VC 直接 Attach 也可以啊,
自己写的代码,还有源码,一看堆栈,一下就知道问题在哪儿,
老邓 2009-06-04
  • 打赏
  • 举报
回复
下载教程看看,这个需要结合帮助文档,系统的学的.
http://search.download.csdn.net/search/windbg
tsinghua605 2009-06-04
  • 打赏
  • 举报
回复
以下是错误分析结果:
0:005> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\kernel32.dll -
*** WARNING: Unable to verify checksum for C:\WINDOWS\system32\packet.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\packet.dll -
*** WARNING: Unable to verify checksum for C:\WINDOWS\system32\WanPacket.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\WanPacket.dll -
*** ERROR: Module load completed but symbols could not be loaded for C:\WINDOWS\system32\odbcint.dll
*** WARNING: Unable to verify checksum for C:\WINDOWS\system32\wpcap.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\wpcap.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\WININET.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\USER32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\GDI32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\RPCRT4.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\OLEAUT32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\SHELL32.dll -
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: IMAGE_NT_HEADERS32 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

FAULTING_IP:
ntdll!DbgBreakPoint+0
7c81a3e1 cc int 3

EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 7c81a3e1 (ntdll!DbgBreakPoint)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: a37a07e0
Parameter[2]: 00000003

FAULTING_THREAD: 0000027c

DEFAULT_BUCKET_ID: STACKIMMUNE

PROCESS_NAME: ip_sctp_m3ua_sccp_ranap_l3_imsiTracking_export.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: a37a07e0

EXCEPTION_PARAMETER3: 00000003

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

ADDITIONAL_DEBUG_TEXT: Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[ffffffff]

LAST_CONTROL_TRANSFER: from 7c83fdd8 to 7c81a3e1

PRIMARY_PROBLEM_CLASS: STACKIMMUNE

BUGCHECK_STR: APPLICATION_FAULT_STACKIMMUNE

STACK_TEXT:
00000000 ip_sctp_m3ua_sccp_ranap_l3_imsiTracking_export+0x0


SYMBOL_NAME: ip_sctp_m3ua_sccp_ranap_l3_imsiTracking_export

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ip_sctp_m3ua_sccp_ranap_l3_imsiTracking_export

DEBUG_FLR_IMAGE_TIMESTAMP: 4a27ae27

STACK_COMMAND: ** Pseudo Context ** ; kb

BUCKET_ID: MANUAL_BREAKIN

IMAGE_NAME: E:\ip_sctp_m3ua_sccp_ranap_l3_imsiTracking_export\release\ip_sctp_m3ua_sccp_ranap_l3_imsiTracking_export.exe

FAILURE_BUCKET_ID: STACKIMMUNE_80000003_E:_ip_sctp_m3ua_sccp_ranap_l3_imsiTracking_export_release_ip_sctp_m3ua_sccp_ranap_l3_imsiTracking_export.exe!Unknown

Followup: MachineOwner
lylm 2009-06-04
  • 打赏
  • 举报
回复
1.运行了一段时间才出错——是否内存泄漏了?
2.打印log也看不出哪里出问题——再加些输出,把关键点打出来
tsinghua605 2009-06-04
  • 打赏
  • 举报
回复
现在是程序要跑很长时间才出错,在环境里跑的话,就不会出问题,只有在脱离了vs2005环境后双击exe文件运行也是运行了一段时间才出错,打印log也看不出哪里出问题,针对这种情况,各位有什么好的办法调试么?
goodname 2009-06-04
  • 打赏
  • 举报
回复
你可以单步调试一下,大概是越界了,结果把堆栈给冲坏了。
tsinghua605 2009-06-04
  • 打赏
  • 举报
回复
就是因为VC直接Attach看不到堆栈信息,才用WinDbg,到现在也不知道为什么用VC不能看到堆栈信息

64,281

社区成员

发帖
与我相关
我的任务
社区描述
C++ 语言相关问题讨论,技术干货分享,前沿动态等
c++ 技术论坛(原bbs)
社区管理员
  • C++ 语言社区
  • encoderlee
  • paschen
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
  1. 请不要发布与C++技术无关的贴子
  2. 请不要发布与技术无关的招聘、广告的帖子
  3. 请尽可能的描述清楚你的问题,如果涉及到代码请尽可能的格式化一下

试试用AI创作助手写篇文章吧