2 comments

Hello,

I will work only for a few more days in the project. I have a lot of
work to finish and so i'm afraid i won't find the time to debug Visual
Studio. Anyway i will try to do it and send you the result.


From a few similar exceptions I could induce that unrelated message&event
handlers are being executed during our COM call into Visual Studio, probably
due to the .NET message pumping habit. As an unmanaged exception is thrown
from within an unmanaged handler, we cannot see its origin from the managed
stacktrace. That's why I had to ask for more detailed stack traces ;) Maybe
we'll know the failing subsystem, at least. However, I'm not 100% sure that
those traces are going to be of great use... That's what it's all about.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

Would it help to receive a memory dump of the deven.exe process when this
happens?

"Serge Baltic" <baltic@intellij.net> wrote in message
news:dc0986bf10d77a8cad05f5d3d0453@news.intellij.net...

Hello,

>
>> I will work only for a few more days in the project. I have a lot of
>> work to finish and so i'm afraid i won't find the time to debug Visual
>> Studio. Anyway i will try to do it and send you the result.
>

From a few similar exceptions I could induce that unrelated message&event
handlers are being executed during our COM call into Visual Studio,
probably due to the .NET message pumping habit. As an unmanaged exception
is thrown from within an unmanaged handler, we cannot see its origin from
the managed stacktrace. That's why I had to ask for more detailed stack
traces ;) Maybe we'll know the failing subsystem, at least. However, I'm
not 100% sure that those traces are going to be of great use... That's
what it's all about.

>


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”

>

0

Please sign in to leave a comment.