Re: System.ExecutionEngineException for certificate object creation
From: Joe Kaplan \(MVP - ADSI\) (joseph.e.kaplan_at_removethis.accenture.com)
Date: 05/03/05
- Previous message: Sushant Bhatia: "Re: System.ExecutionEngineException for certificate object creation"
- In reply to: Sushant Bhatia: "Re: System.ExecutionEngineException for certificate object creation"
- Next in thread: Sushant Bhatia: "Re: System.ExecutionEngineException for certificate object creation"
- Reply: Sushant Bhatia: "Re: System.ExecutionEngineException for certificate object creation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 2 May 2005 22:25:19 -0500
I'm not sure how you can conclude that the vendor component is not at fault
here just because it works some of the time. These types of errors tend to
be hard to track down and there might be a combination of symptoms that
causes the problem.
Changing to a release build might help with the problem (l've seen that
before personally), but that does not bode well that the problem is solved.
Still, it is worth a shot.
If stack SIZE was an issue, you would probably have gotten a
StackOverflowException like you get from infinite recursion and such. I'm
still betting on some kind of corruption that happened due to some unmanaged
code doing something to memory that it should not have.
The classic way to debug this would be to use a lower level debugger like
windbg with the SOS extension loaded, but there is steep learning curve
there if you are not already skilled. I can't be of any assistance with
that. You might consider posting on the dotnet.framework.clr newsgroup to
see if they have any suggestions as a lot of the more hard core CLR guys
hang out there.
Best of luck,
Joe K.
"Sushant Bhatia" <sushant.bhatia@gmail.com> wrote in message
news:1115082517.794761.214120@z14g2000cwz.googlegroups.com...
> Hi Yunus & Joe,
>
> I don't think its a SecureBlackBox issue because I am using the very
> same call throughout my application in different functions. Its only
> this specific call to object creation that is throwing the exception.
> If I comment it out, no exception is thrown. The application is a
> Client/Server chat program and the exception is being thrown in one
> chat client. I used the very same object creation call in the server
> right before I send the data to see if its an issue with SecureBlackBox
> and it worked fine.
>
> I don't think the CLR is corrupted because it runs all the application
> I have as normal.
>
> 2 follow up questions:-
>
> -A friend of mine suggested that I compile the code above for release
> instead of debug as I am doing now because the CLR for release is
> "different" to the debug CLR. Is this true? Is there "really" a
> different CLR for release and debug?
>
> -Another friend suggested I look at the stack size to see if there were
> any issues in there. Can the ExecutionEngineException be thrown because
> of Stack "miscalculations"?
>
> I will try this on another machine to see if it still throws the
> exception. I'll post a bit later with the results of that.
>
> Thanks for your replies.
> Sushant Bhatia
>
- Previous message: Sushant Bhatia: "Re: System.ExecutionEngineException for certificate object creation"
- In reply to: Sushant Bhatia: "Re: System.ExecutionEngineException for certificate object creation"
- Next in thread: Sushant Bhatia: "Re: System.ExecutionEngineException for certificate object creation"
- Reply: Sushant Bhatia: "Re: System.ExecutionEngineException for certificate object creation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|