Re: The infamous R6025 runtime error

• Previous message: Maka Sili: "Re: Force Minimize to taskbar"
• In reply to: Antti Keskinen: "Re: The infamous R6025 runtime error"
• Messages sorted by: [ date ] [ thread ]

Date: Sat, 5 Feb 2005 10:16:48 -0600

"Antti Keskinen" <antti.keskinen@REMOVEME.ee.tpu.fi> wrote in message
news:%23%23gXXN2CFHA.2032@tk2msftngp13.phx.gbl...
> Hello !
>
>> Please excuse my incredulity, but if you have a problem that occurs only
>> when a certain software product is installed and the problem does not
>> occur when that product is not installed, how do you conclude that the
>> problem is somehow associated with a different product? I may be off base
>> here, but I believe a module hooked to devenv could throw an error that
>> devenv was not programmed to handle. thus causing the error report you
>> mentioned.
>
> Due to the Visual Assist Team. After doing two weeks of intense debugging,
> sending error reports, logs and screenshots plus ways to reproduce the
> problem, the team could not find the reason why Visual Studio crashed.
> When the crash occurs, VA does not return any error codes or cause an
> errorneous situation. It shuts itself down properly and correctly. The
> crash itself occurs after VA has already closed.
>
> However, your amazement on the situation is understandable. VA team came
> to the conclusion that this behaviour is caused by a DLL which both VA and
> VS utilize and for some reason this DLL can't handle it's task. Or, this
> is what they told me. It can, of course, be that this isn't true. I
> couldn't know if this was the case.
>
>> I'm also intrigued by your assertion that you can open a source code file
>> in Visual Studio .NET 2003 and have Visual Studio create a temporary
>> solution around it. I would really like to take advantage of such a
>> feature in the classroom when showing demo code. How can one access the
>> temporary solution, compile the code and run the executable? Currently, I
>> am creating an empty Win32 console solution, then adding the source code
>> to the solution to show demos.
>
> Ahh, you've misunderstood me. You can try this situation yourself, just
> open up Visual Studio, and then use the Open command to open a lone code
> or header file. Now, if the solution explorer is not visible, use the View
> menu to display it. You can see that VS created a solution called
> 'Solution0' and placed the code file in folder 'Miscellaneous files'. It
> does not create a project, however, thus it is not possible to compile and
> debug/execute it. My belief is that because VA stores project-specific
> information about variables and symbols, then a situation where you have a
> solution but no projects causes it to misfunction. The problematic
> situation is that if I create a blank solution manually, and add then use
> 'Open' to open the lone file, it still creates a 'Miscellaneous files'
> folder, but does not crash..
>
> UPDATE:
>
> After a set of long hours working with the problem, I've isolated it. I
> didn't notice that I had Rational Rose Add-In Manager running in Visual
> Studio IDE. Disabling this add-in from starting eliminated the problem. So
> it seems to be an incompatiblity with VA and Rose.
>
> -Antti Keskinen
>
>
>
>> "Antti Keskinen" <antti.keskinen@REMOVEME.ee.tpu.fi> wrote in message
>> news:OCJQOFsCFHA.1836@tk2msftngp13.phx.gbl...
>>> Hello ppl !
>>>
>>> Since this newsgroup is a place where Microsoft MVPs or related visit
>>> somewhat often, could someone give me an advice with possible causes of
>>> this error. Note that it does not happen with the programs I write, but
>>> with Visual Studio .NET 2003 itself. It seems to appear only when I have
>>> the Visual Assist add-in installed. Removing the add-in fixes this
>>> error, but using VA is pretty much a necessity due to the bad
>>> functionality of IntelliSense.
>>>
>>> However, extensive analysis with the VA team has revealed that this bug
>>> is related to somewhere else than the actual VA product. The easiest way
>>> to reproduce it is to open a lone file in Visual Studio, that is, a file
>>> which doesn't have a solution attached to it. VS creates a temporary
>>> solution for it, and closing this solution causes the crash. The crash
>>> informs me that the place where this error occurs is 'devenv.exe', which
>>> is the VS executable as far as I know.
>>>
>>> So, does anyone have any clue where this problem originates from ?
>>> Looking in Internet, it seems to appear randomly on different Microsoft
>>> products (such as Office or SharePoint), but never there is a true
>>> explanation of the causes of this. Any and all suggestions related are
>>> appreciated.
>>>
>>> -Antti Keskinen
>>>
>
Thanks very much, Antti, for the update and further clarification on the
temporary solution. I tried your steps and now see exactly what you mean.
Glad you got the crash thing sorted.

• Previous message: Maka Sili: "Re: Force Minimize to taskbar"
• In reply to: Antti Keskinen: "Re: The infamous R6025 runtime error"
• Messages sorted by: [ date ] [ thread ]