M
Mike
Folks,
Been banging my head on this one error:
Managed Debugging Assistant 'FatalExecutionEngineError' has detected
a problem in '................\Testapi1.exe'.
Additional Information: The runtime has encountered a fatal error.
The address of the error was at 0x79f387cc, on thread 0xc08. The
error code is 0xc0000005. This error may be a bug in the CLR or in
the unsafe or non-verifiable portions of user code. Common sources
of this bug include user marshaling errors for COM-interop or
PInvoke, which may corrupt the stack.
The exception suddenly began to appear and then after doing a few
things, no longer. I am not sure what caused it or what fixed it
because my DLL was working solid for the past 2 days and I traced all
the WIN32 imported/marshalled dll.
I can't be certain but it did cross my mind if deleting some project
file was going to be some issue.
I guess my question is could deleting those My Project files
cause some .NET binding issue that I have ignored up to this
point?
What I did was began to clean up my DLL project, like removing blocks
of test functions no longer used, adding comments. No changes to the
actual working code.
But what I also did was delete the some files under "My Project".
Specifically:
Resources.resx
Resources.Designer.vb
Sedttings.Designer.vb
Settings.Settings.
Before I deleted them I zipped them just in case. I figured if I
wasn't using them, so why have them. But I kept:
Application.myapp
Application.Designer.vb
AssemplyInfo.Vb
I ran the code and it all looked good. But what I did not run is the
more complex marshalled callback test suite.
When I did run the callback test suites shortly ago, I started to get
the above.
I put back the My Project files did a rebuild. The exception remained.
Under debug I noticed two testapi1.exe, the display said one was
mananged and the other native. I tried many things thinking maybe
there was some issue between the EXE and DLL, like
1) Play around with the switch
[X] Enabled the Visual Studio Hosting Process
on and off and didn't see to matter
2) Copied the CALLBACK code logic back into the main exe
process so there was no crossing with the DLL.
When I did the 2nd, it worked again.
Here's the odd thing:
I deleted the callback logic in the main code so now uses the DLL
again and now it still working now.
Did deleting those My Projects caused this?
Whats the purpose of using a VS Hosting Process?
Is that why I have two testapi1.exe in memory?
Thanks
--
Been banging my head on this one error:
Managed Debugging Assistant 'FatalExecutionEngineError' has detected
a problem in '................\Testapi1.exe'.
Additional Information: The runtime has encountered a fatal error.
The address of the error was at 0x79f387cc, on thread 0xc08. The
error code is 0xc0000005. This error may be a bug in the CLR or in
the unsafe or non-verifiable portions of user code. Common sources
of this bug include user marshaling errors for COM-interop or
PInvoke, which may corrupt the stack.
The exception suddenly began to appear and then after doing a few
things, no longer. I am not sure what caused it or what fixed it
because my DLL was working solid for the past 2 days and I traced all
the WIN32 imported/marshalled dll.
I can't be certain but it did cross my mind if deleting some project
file was going to be some issue.
I guess my question is could deleting those My Project files
cause some .NET binding issue that I have ignored up to this
point?
What I did was began to clean up my DLL project, like removing blocks
of test functions no longer used, adding comments. No changes to the
actual working code.
But what I also did was delete the some files under "My Project".
Specifically:
Resources.resx
Resources.Designer.vb
Sedttings.Designer.vb
Settings.Settings.
Before I deleted them I zipped them just in case. I figured if I
wasn't using them, so why have them. But I kept:
Application.myapp
Application.Designer.vb
AssemplyInfo.Vb
I ran the code and it all looked good. But what I did not run is the
more complex marshalled callback test suite.
When I did run the callback test suites shortly ago, I started to get
the above.
I put back the My Project files did a rebuild. The exception remained.
Under debug I noticed two testapi1.exe, the display said one was
mananged and the other native. I tried many things thinking maybe
there was some issue between the EXE and DLL, like
1) Play around with the switch
[X] Enabled the Visual Studio Hosting Process
on and off and didn't see to matter
2) Copied the CALLBACK code logic back into the main exe
process so there was no crossing with the DLL.
When I did the 2nd, it worked again.
Here's the odd thing:
I deleted the callback logic in the main code so now uses the DLL
again and now it still working now.
Did deleting those My Projects caused this?
Whats the purpose of using a VS Hosting Process?
Is that why I have two testapi1.exe in memory?
Thanks
--