LoadLibrary导致访问冲突与0xC0000005

LoadLibrary导致访问冲突与0xC0000005

本文介绍了LoadLibrary导致访问冲突与0xC0000005的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述




我正在研究一种遗留产品,它可以加载和卸载我们的DLL(比如DLL A)很多次在特定的工作流程中。


虽然它多次成功加载/卸载DLL A,但它在一个点上因访问冲突错误而失败。我们没有得到进一步的线索,因为应用程序崩溃。



Windows事件查看器为我提供了这些信息:

错误的应用程序名称:MyApp .exe,版本:8.10.0.651,时间戳:0x5cd12bdb

错误模块名称:clr.dll,版本:4.7.3394.0,时间戳:0x5c537182

异常代码: 0xc0000005

故障偏移:0x0045510d

故障流程ID:0x20a0

故障应用程序启动时间:0x01d504a5b280527f

故障应用程序path:C:\ Users \I_SDU \source \ Workspaces \ MyApp\build \Debug \ x86 \ MyApp.exe

错误模块路径:C:\ Windows \ Microsoftoft.NET\Framework\v4.0.30319\clr.dll

报告ID:a74cfc6e-451a-45be-b060-e9203f56d580

错误包全名: 
$
错误的包相关应用程序ID: 



主要是C ++ / MFC代码,而且错误的是错误模块是clr.dll。不确定会出现什么问题。

感谢有关如何解决此崩溃问题的任何意见。



TIA,

Jy

解决方案

Hi,

I'm working on a legacy product, which loads and unloads one of our DLLs (say DLL A) quite a few times during a particular workflow.

While it successfully loads/unloads DLL A multiple times, it fails at one point with an Access Violation error. We get no further clues, since the application just crashes.

The Windows Event Viewer gives me this information:
Faulting application name: MyApp.exe, version: 8.10.0.651, time stamp: 0x5cd12bdb
Faulting module name: clr.dll, version: 4.7.3394.0, time stamp: 0x5c537182
Exception code: 0xc0000005
Fault offset: 0x0045510d
Faulting process id: 0x20a0
Faulting application start time: 0x01d504a5b280527f
Faulting application path: C:\Users\I_SDU\source\Workspaces\MyApp\build\Debug\x86\MyApp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: a74cfc6e-451a-45be-b060-e9203f56d580
Faulting package full name: 
Faulting package-relative application ID: 

It is mostly C++/ MFC code, and surprisingly the Faulting module is clr.dll. Not sure what is going wrong.
Appreciate any inputs on how to resolve this crash issue.

TIA,
Jy

解决方案


这篇关于LoadLibrary导致访问冲突与0xC0000005的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

07-28 06:48