Re: Nasty Problem
- From: "Steve Wheeler" <swheeler@xxxxxxxxxxxxxx>
- Date: Fri, 6 Oct 2006 08:24:33 -0400
No globals are defined; there are 2 static mdthods, but other than that no
static variables either. Commenting new code is not simple beause the change
represents the merging of 2 libraries and there are dependancies through out
the main application which is some 50K+ lines of code. Any other thoughts?
"Maksim Libenson" <Maksim.Libenson@xxxxxxxxx> wrote in message
news:1160133300.577170.294230@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
Do you have any global variables defined in your code? That would be
first thing that I will check. Otherwise just comment all new code and
start uncommenting gradually untill you will hit the problem.
Max
http://ceeplusplus.com
S Wheeler wrote:
I have a REALLY nasty problem and could use some expert help.
I have two mixed mode apps. Each uses a mixed mode DLL that exports a
couple
of classes. There is no dll main as it is not needed. This was working
fine
until a couple of days ago when I added some (a lot of) new code to the
dll.
The apps generally do not run at the same time. Every thing compiles and
links OK. But at run time I now immediately get :
The application failed to initialize properly (0xc0000005). Click on OK
to
terminate the application.
I have to click OK twice and then get:
Unhandled exceptionat 0x7c964ed1 (ntdll.dll) in myApp.exe: 0xC0000005:
Access violation.
This occurs very earily in the app loading and I can not even hit a break
point.
I have read all the google stuff about permissions and viruses but I am
sure
that is not the problem here. After exhaustive debugging, I noted that in
one of my GUI apps (the simpler one) I had some MessageBox calls that
would
be called if certain error conditions occured. I was able to determine
that
the presence of these calls was enough to cause the problem - so I
removed
them and that application started working fine. I had already been
suspecting some sort of run time library mismatch and this seems to
confirm
that. I have removed all MessageBox calls in my other app but it still
crash
immediately after starting.
My first question: what libraries would MessageBox require (implicitly
linked) and what might be some other library calls that may be causing
similar problems in my other application. I am using /clr and
Multi-threaded
Debug (/MTd) for the application and /clr and Multi-threaded Debug DLL
(/MDd) for the DLL. This is such a subttle problem, it must be some sort
of
run time mismatch deep under the covers and the error messaages and
posted
articles are missleading at best. Could this be related to the app
Message
Loop?
Kindly Experts, I could use your help!
.
- References:
- Nasty Problem
- From: S Wheeler
- Re: Nasty Problem
- From: Maksim Libenson
- Nasty Problem
- Prev by Date: Re: Nasty Problem
- Next by Date: VC 8 <-> VC 7.1 compatability, System.TypeLoadException: Method XXX does not have an implementation
- Previous by thread: Re: Nasty Problem
- Next by thread: Re: Nasty Problem
- Index(es):
Relevant Pages
|
