WTL DLL runtime access violation

Question

0.00/5 (No votes)

See more:

The start reason is that I want to change a WTL exe project to dll project so that I could use it as plugin in another project. Those code worked well in the exe, but got exception in the DLL. I tracked it down, initialization is fine, when it goes to the

CWindowImpl::create->
T::GetWndClassInfo().Register(&m_pfnSuperWindowProc)->
... if (FAILED(lock.Lock())) then

C++

inline HRESULT CComCritSecLock< TLock >::Lock() throw() 
{ HRESULT hr; 
ATLASSERT( !m_bLocked ); 
hr = m_cs.Lock();//exception caught 
if( FAILED( hr ) ) 
{ return( hr ); } 
m_bLocked = true; 
return( S_OK ); } code

Posted 6-Feb-13 20:46pm

lan yuan

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

lan yuan · Answer 1 · 2013-03-06T23:25:00

This problem has been solved, the reason is No call to InitializeCriticalSection(...);for I used the loadlibrary(*.dll),which leave the global variables(_AtlWinModule，_AtlBaseModule,_AtlComModule which is used by ATL components later) uninitialized. So in this situation, Adding _CRT_INIT to the DLLMain could overcome the access vialation, the crt_INIT function could help initialize the related global varible. like :

add _CRT_INIT in the:

C++

DLLMain(ul_reason_for_call)
 {
 case DLL_PROCESS_ATTACH:
  {
   _CRT_INIT(hModule,ul_reason_for_call,lpReserved);
}