| T O P I C R E V I E W |
| enigma |
Posted - Nov 12 2007 : 02:13:06 AM
I got this message when I tried to search the occurrence of a class:
Runtime Error!
Program: C:\\Program Fil...
R6025
-pure virtual function call
After this dialog box occurred, the whole Visual Studio will exit.
OK, I admit that I can't reproduce it, since it appears only sometimes, but not all of the time. The object I tried to find is just a normal class; it inherits some interfaces, but is not inherited by other classes.
This is my VA information:
VA_X.dll file version 10.4.1616.0 built 2007.11.08
Licensed to:
VA X: [email protected] (1-user license) Support ends 2008.10.12
DevEnv.exe version 7.10.6030.0
msenv.dll version 7.10.6030.0
Font: Courier New 13(Pixels)
Comctl32.dll version 5.82.2900.2982
Windows XP 5.1 Build 2600 Service Pack 2
2 processors
Platform: Win32
Stable Includes:
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\include;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\include;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\PlatformSDK\\include\\prerelease;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\PlatformSDK\\include;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\SDK\\v1.1\\include;
Other Includes:
Stable Source Directories:
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\src\\mfc;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\src\\atl;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\crt\\src;
These are my visual studio info:
Microsoft Visual Basic .NET 69462-270-0000007-18064
Microsoft Visual C# .NET 69462-270-0000007-18064
Microsoft Visual C++ .NET 69462-270-0000007-18064
Automated Build Studio
Crystal Reports for Visual Studio .NET AAP50-GS00000-U7000RN
Microsoft Visual Studio .NET 2003 Service Pack 1 (KB918007)
Visual Assist X
Remotesoft .NET Explorer
TestDriven.NET 2.8.2130 Personal
|
| 12 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Aug 28 2009 : 11:04:11 AM
How are you leaving your machine over night? Is it turned on and running? Is it suspended? Hibernated?
If you close and restart the IDE before loading the solution in the morning do you still see this crash?
Next time you see the crash can you try saving out a mini dump file and sending this to us please, as explained in this FAQ:
http://docs.wholetomato.com?W303
hopefully this will give us some clues as to the problem. |
| jamesford42 |
Posted - Aug 27 2009 : 2:59:33 PM
It seems to happen when I first come in, in the mornings.
I do a project update, regenerate projects, open project - and crash. After restarting VS ( which was left running but with no project open overnight ) it does not happen a second time - until tomorrow morning.
VA_X.dll file version 10.5.1727.0 built 2009.06.12
Licensed to:
VA X: [email protected] (1-user license) Support ends 2010.07.16
DevEnv.exe version 8.0.50727.762
msenv.dll version 8.0.50727.762
Font: Consolas 15(Pixels)
Comctl32.dll version 6.0.2900.5512
Windows XP 5.1 Build 2600 S
2 processors (x86)
Platform: Custom
Stable Includes:
Other Includes:
Stable Source Directories:
|
| accord |
Posted - Dec 11 2007 : 05:37:24 AM
quote:
Originally posted by tomate
i didn't test it until now, but wouldn't it be possible that VA lets me trigger another Find References and stops the current running Find References before it starts the new one?
In builds 15xx VAX restarted the find references. The current behavior is new to builds 16xx. |
| tomate |
Posted - Dec 11 2007 : 04:28:13 AM
quote:
Originally posted by feline
tomate this should be fixed in VA 1623. VA will not let you trigger a second Find References while the first one is running.
i didn't test it until now, but wouldn't it be possible that VA lets me trigger another Find References and stops the current running Find References before it starts the new one?
|
| enigma |
Posted - Dec 10 2007 : 11:17:37 PM
Yes, I triggered the problem when I ran two find references together |
| feline |
Posted - Dec 10 2007 : 06:11:34 AM
tomate this should be fixed in VA 1623. VA will not let you trigger a second Find References while the first one is running.
enigma does this crash seem to be related to running two Find References at the same time? Or does it seem to be a separate problem? |
| enigma |
Posted - Dec 10 2007 : 04:03:27 AM
Hi,
This is the call stack I managed to recover:
> 01c2d59e()
VA_X.dll!1ed09524()
VA_X.dll!1eecfbc5()
VA_X.dll!1ed8cdf7()
VA_X.dll!1ed8cfc7()
VA_X.dll!1ed8d232()
VA_X.dll!1eda44ec()
VA_X.dll!1ef09de7()
VA_X.dll!1eefb644()
VA_X.dll!1ef08df1()
VA_X.dll!1ef08bd2()
VA_X.dll!1ef09175()
VA_X.dll!1ef0925e()
VA_X.dll!1ef095b2()
VA_X.dll!1ef095ba()
ntdll.dll!7c910833()
VA_X.dll!1ef096be()
VA_X.dll!1eefb33b()
ntdll.dll!7c9037bf()
ntdll.dll!7c90378b()
ntdll.dll!7c937860()
ntdll.dll!7c90eafa()
|
| tomate |
Posted - Dec 10 2007 : 03:46:23 AM
On Visual Studio 6.0 i can reproduce this error:
Start finding references of a function and before the search has finished start finding references for another function.
This is the case for VA_X.dll file version 10.4.1619.0 built 2007.11.20 |
| feline |
Posted - Nov 13 2007 : 08:00:32 AM
Once the IDE crashes or hangs launch a second instance of VS2003, but do not load any solution in this second instance.
Open the Tools menu and select "Debug Process..."
In the dialog that appears select "devenv.exe" in the Available Processes list and press the "Attach" button.
Once the second IDE has finished attaching close the "Process" dialog
Now open the Debug menu and select "Break All"
If the Call Stack window is not visible then show it by opening the Debug menu and selecting "Windows -> Call Stack"
You should now be able to click into the Call Stack window, select all of the text via CTRL-A then copy / paste it into your reply.
Hopefully this all makes sense. |
| enigma |
Posted - Nov 12 2007 : 7:25:42 PM
quote:
Originally posted by feline
Have you seen this with previous versions of VA? I am wondering if this is a new problem.
Clearly it is a bad problem.
Next time this happens can you try running a second instance of VS2003 and attaching the debugger, to try and get a call stack?
Good idea, may I know how to do this? |
| feline |
Posted - Nov 12 2007 : 07:50:14 AM
Have you seen this with previous versions of VA? I am wondering if this is a new problem.
Clearly it is a bad problem.
Next time this happens can you try running a second instance of VS2003 and attaching the debugger, to try and get a call stack? |
| enigma |
Posted - Nov 12 2007 : 02:14:26 AM
I am editing my source code in C# when the problem occurred. All of the projects inside the solution were C#; there was no cross-language project in the edited solution. |
