程序在User32.dll中不断死亡 [英] Program keeps dying in User32.dll

查看:69
本文介绍了程序在User32.dll中不断死亡的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我遇到一个问题,我的程序在User32.dll中死了。问题是我不知道它是如何达到这一点的,或者是什么入口点。这是应用程序日志的转储。我知道异常代码告诉我它是一个内存访问错误,
这可能意味着一个错误的指针,但我需要帮助的是确定什么是实际的函数调用,我认为有一种方法可以得到来自Exception Offset,在这种情况下是0x00018172。如果有帮助,这是一个Window 7。


日志名称:应用程序源:应用程序错误日期:1/24/2017 10:51:40 AM事件ID:1000任务类别:(100)级别:错误关键词:经典用户:N / A计算机:5FBCFB2 描述:
错误应用程序名称:PARSEntr.exe,版本:0.0.0.0,时间戳:0x5862e934错误模块名称:USER32.dll,版本:6.1.7601.19061,时间戳:0x56423973异常代码:0xc0000005错误偏移量:0x00018172错误进程id :0x6d0错误应用程序
开始时间:0x01d276621d8ee98d错误应用程序路径:C:\Tiburon\Prd \Bin \ PARSEntr.exe错误模块路径:C:\ windows \ syswow64 \ USER32.dll报告Id:6072d9ff-e255-11e6-8929-f48e38d14052事件Xml:<事件x
m l n s = " h t t p / / s c h e m a s m c r o s o f t c o m / w n / 2 0 0 4 / 0 8 / e v ents / event">
<系统><提供商名称="应用程序错误" &&;< EventID限定符=" 0"> 1000< / EventID>< ;级别> 2< / Level><任务> 100< /任务><关键字> 0x80000000000000< / Keywords>< TimeCreated SystemTime =" 2017-01-24T16:51:40.000000000Z"
/> ;< EventRecordID> 12753< / EventRecordID>< Channel> Application< / Channel>< Computer> 5FBCFB2.milwpd.org< / Computer>< Security />< / System>< EventData>< Data> ; PARSEntr.exe< / Data>< Data> 0.0.0.0< / Data>
< Data> 5862e934< / Data>< Data> USER32.dll< / Data>< Data> 6.1。 7601.19061< / Data>< Data> 56423973< / Data>< Data> c0000005< / Data>< Data> 00018172< / Data>< Data> 6d0< / Data>< Data> 01d276621d8ee98d< / Data> ;
< Data> C:\ Tiburon\Prd \Bin \ PARSEntr.exe< / Data> ;< Data> C:\windows \ syswow64 \ USER32.dll< / Data> <数据> 6072d9ff-e255-11e6-8929-f48e38d14052< /数据与GT; < / EVENTDATA> < / Event>
< u5:p>< / u5:p>


< u5:p>< / u5:p>

解决方案

在调试器中运行程序,当发生异常时,检查调用堆栈以找到问题的根源点。

I am having an issue where my program keeps dying in User32.dll. The thing is I have no idea how it got to that point, or what entry point is. Here is the dump of the application log. I know that the Exception Code is telling me it is an Memory Access error, which probably means a bad pointer, but what I need help will is determining what is the actual function call which I assume there is a way to get that from the Exception Offset which in this case is 0x00018172. If it helps this is a Window 7.

Log Name: Application Source: Application Error Date: 1/24/2017 10:51:40 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: 5FBCFB2 Description: Faulting application name: PARSEntr.exe, version: 0.0.0.0, time stamp: 0x5862e934 Faulting module name: USER32.dll, version: 6.1.7601.19061, time stamp: 0x56423973 Exception code: 0xc0000005 Fault offset: 0x00018172 Faulting process id: 0x6d0 Faulting application start time: 0x01d276621d8ee98d Faulting application path: C:\Tiburon\Prd\Bin\PARSEntr.exe Faulting module path: C:\windows\syswow64\USER32.dll Report Id: 6072d9ff-e255-11e6-8929-f48e38d14052 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-01-24T16:51:40.000000000Z" /> <EventRecordID>12753</EventRecordID> <Channel>Application</Channel> <Computer>5FBCFB2.milwpd.org</Computer> <Security /> </System> <EventData> <Data>PARSEntr.exe</Data> <Data>0.0.0.0</Data> <Data>5862e934</Data> <Data>USER32.dll</Data> <Data>6.1.7601.19061</Data> <Data>56423973</Data> <Data>c0000005</Data> <Data>00018172</Data> <Data>6d0</Data> <Data>01d276621d8ee98d</Data> <Data>C:\Tiburon\Prd\Bin\PARSEntr.exe</Data> <Data>C:\windows\syswow64\USER32.dll</Data> <Data>6072d9ff-e255-11e6-8929-f48e38d14052</Data> </EventData> </Event><u5:p></u5:p>

<u5:p></u5:p>

解决方案

Run the program in the debugger and when the exception occurs examine the call stack to find the source of the problem.


这篇关于程序在User32.dll中不断死亡的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆