EngineExecutionException

  • Thread starter Thread starter n_o_s_p_a__m
  • Start date Start date
N

n_o_s_p_a__m

This exception is not even listed in MSDN, and my program threw it.

Anyone have any clues as to why?

The program is a multithreaded background process (Windows
Application) that runs constantly. It makes heavy use of ADO and has a
GUI window which is updated as the process does its work.

-KJ
 
KJ,

Can you give the stack trace, and any message information that you get
with the exception?
 
The instance of the CLR debugger takes you straight to the
disassembly. It was uncaught, probably uncatchable.

Nicholas Paldino said:
KJ,

Can you give the stack trace, and any message information that you get
with the exception?

--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

n_o_s_p_a__m said:
This exception is not even listed in MSDN, and my program threw it.

Anyone have any clues as to why?

The program is a multithreaded background process (Windows
Application) that runs constantly. It makes heavy use of ADO and has a
GUI window which is updated as the process does its work.

-KJ
Click to expand...
Click to expand...
 
Hi,
have you tried System.AppDomain.CurrentDomain.UnhandledException event
to try to handle the exception?

Sunny

The instance of the CLR debugger takes you straight to the
disassembly. It was uncaught, probably uncatchable.

Nicholas Paldino said:
KJ,

Can you give the stack trace, and any message information that you get
with the exception?

--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

n_o_s_p_a__m said:
This exception is not even listed in MSDN, and my program threw it.

Anyone have any clues as to why?

The program is a multithreaded background process (Windows
Application) that runs constantly. It makes heavy use of ADO and has a
GUI window which is updated as the process does its work.

-KJ
Click to expand...
Click to expand...
Click to expand...
 
This should only occur when something really bad has happened (bad compiler
output, for instance).

Are you able to isolate the area that causes it? Even if you go into
dissassembly, there should still be a stack trace around somewhere.

And, you're using ADO with COM interop?

-mike
MVP
 
You should still be able to see a stack trace. Of particular importance will
be the system assembly that threw the exception.

This exception typically is caused by internal memory corruption which is
usually caused by unmanaged code stomping over internal data - if you do a
lot of P/Invoke I'd start looking there. I've also seen it occur in a
heavily multi-threaded app with multiple appdomains.

n_o_s_p_a__m said:
The instance of the CLR debugger takes you straight to the
disassembly. It was uncaught, probably uncatchable.

"Nicholas Paldino [.NET/C# MVP]" <[email protected]> wrote
in message news: said:
KJ,

Can you give the stack trace, and any message information that you get
with the exception?

--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

n_o_s_p_a__m said:
This exception is not even listed in MSDN, and my program threw it.

Anyone have any clues as to why?

The program is a multithreaded background process (Windows
Application) that runs constantly. It makes heavy use of ADO and has a
GUI window which is updated as the process does its work.

-KJ
Click to expand...
Click to expand...
Click to expand...
 
All: I closed the debugger after looking at the disassembly, so I
believe I may be SOL in terms of getting the statck trace, unless
there's some log kept by .net somewhere where these kinds of things
get logged.

So, please tell me step-by-step what to do next time this happens (as
it may)!

Thanks,
KJ
 
Step-by-step? Look at the stack trace to see if you can find out where this
is happening. Then, go look at that code in ILDASM and the original
language and see if you can find a problem. The clr NG might help at that
point.
-mike
MVP
 
Back
Top