| Author |
 Topic  |
|
|
jameso
Ketchup Master
United Kingdom
83 Posts |
 Posted - Jun 30 2006 : 11:10:36 AM
|
Opening a C# file in a large solution (80ish projects - mainly C/C++) in VS2005 I get a pure virtual function call. Its reproducable & goes away if I disable VAX. It was present in 1525, but I upgraded to see if it was fixed. Still present in 1526
I have a minidump if that would be useful - contact me by email.
Cheers
James
|
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Jul 01 2006 : 4:09:30 PM
|
| i will chaise support about this. we are getting occasional reports of this, but so far it all seems quite random, and i have yet to have this problem myself. |
zen is the art of being at one with the two'ness |
 |
|
|
support
Whole Tomato Software
5566 Posts |
|
|
jameso
Ketchup Master
United Kingdom
83 Posts |
Posted - Jul 02 2006 : 4:06:26 PM
|
I've got no other addins & the IDE is VS2005 RTM.
As I said, it's reproducable (every time) and I can send you log files or a minidump if it would help
James |
|
|
|
Admin
Whole Tomato Software
USA
74 Posts |
Posted - Jul 02 2006 : 11:50:52 PM
|
| We'll take a zip of the minidump. Send via email to [email protected] |
|
|
|
jameso
Ketchup Master
United Kingdom
83 Posts |
Posted - Jul 03 2006 : 04:52:52 AM
|
quote:
Originally posted by Admin
We'll take a zip of the minidump. Send via email to [email protected]
Done
James |
|
|
|
wilstark
Junior Member
USA
22 Posts |
Posted - Jul 06 2006 : 3:01:41 PM
|
| I have seen this also in 1526. Occurs seemingly randomly when switching between files, e.g. "Alt-W 2". Sorry I don't have any more information. |
|
|
|
wilstark
Junior Member
USA
22 Posts |
Posted - Jul 06 2006 : 5:29:36 PM
|
After upgrading to 1528, I'm also seeing it when swiching between windows the same way. (VC 2003).
Then, after downgrading to 1525, it happened when opening a new file using the standard File | Open... dialog. I opened the file after loading the workspace, when VA-X was still indicating that it was parsing files down in the status bar. |
Edited by - wilstark on Jul 06 2006 5:36:28 PM |
|
|
|
Admin
Whole Tomato Software
USA
74 Posts |
Posted - Jul 06 2006 : 7:37:03 PM
|
| We are scrutinizing the minidump we received and are hunting for the culprit. It's like finding a needle in a haystack, after someone has spread the haystack all over the field. |
|
|
|
John_H_Bergman
Tomato Guru
USA
198 Posts |
Posted - Jul 06 2006 : 10:00:30 PM
|
| I have this too, the only other addin I have on one machine is InstallShield. On the other (notebook) where I have also received it, I have NO other addin. I had this in 1526 and 1528. I posted sometime ago when I first saw it as well. (maybe that will provide a clue as to what version it was introduced). |
John H. Bergman
CTO
SiliconZone
[email protected]
To Send email, remove the .online. |
|
|
|
Sergei
Starting Member
Ukraine
1 Posts |
Posted - Jul 07 2006 : 08:42:31 AM
|
I have the problem with 1528 on VS2003 when open C++ solution with 2 projects.
I delete ncb-file and suo-file and now everything is OK.
Sergei |
|
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Jul 08 2006 : 2:52:30 PM
|
| can anyone else who is getting this try deleting the ncb file as well? some IDE's (not sure about VS2005) have a long tradition of corrupting their own ncb files, which can then cause them to crash, but not normally like this. |
zen is the art of being at one with the two'ness |
|
|
|
jameso
Ketchup Master
United Kingdom
83 Posts |
Posted - Jul 08 2006 : 4:42:39 PM
|
I deleted my ncb (all 100M of it) and upgraded to 1528 and have since had only one pure virtual call, but that didn't seem to be the same problem (it was while debugging, but not changing window)
I knew you'd be happy :/
James |
|
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Jul 09 2006 : 11:20:07 AM
|
to be honest this does not sound like a corrupt ncb file problem to me, but it would be nice if it was that easy.
the developers are still picking through the minidump file, which seems to be very show going. if you can find any form of pattern or trigger, just enough so that you can enable VA's logging shortly before this happens then that might help us.
when you get the crash, is there any way you could get a call stack by attaching a second IDE? apparently the stack in the minidump is rather corrupt. |
zen is the art of being at one with the two'ness |
Edited by - feline on Jul 09 2006 11:20:59 AM |
|
|
|
support
Whole Tomato Software
5566 Posts |
|
|
jameso
Ketchup Master
United Kingdom
83 Posts |
Posted - Jul 09 2006 : 1:07:04 PM
|
quote:
Originally posted by feline
when you get the crash, is there any way you could get a call stack by attaching a second IDE? apparently the stack in the minidump is rather corrupt.
That's exactly how I created the minidump...
I'll have another try next time it happens |
|
|
|
John_H_Bergman
Tomato Guru
USA
198 Posts |
Posted - Jul 10 2006 : 5:02:56 PM
|
| You might try using ADPlus from the DDK, it seems to create minidumps when other tools fail, or create one with a corrupt call stack. |
John H. Bergman
CTO
SiliconZone
[email protected]
To Send email, remove the .online. |
|
|
|
wilstark
Junior Member
USA
22 Posts |
Posted - Jul 17 2006 : 2:24:47 PM
|
Running VA-X 1530 I have just now seen the pure virtual function call issue again.
I'd just opened a .sln with about 10 .vcproj files (either makefile or C++ DLL/EXE projects) in which some files (undoubtedly .h or .cpp) were initially opened in the editor. I then used 'open file in workspace' to open a new file from one of the projects (happened to be an .idl file). Then as it was opening the new file, I got the error. At the time when I opened the new file, I was still getting 'VA-X is parsing' messages in the status bar. (It seemed to me that in previous builds, the pure-virtual error occurred more frequently if VA-X was parsing in the background when you switched between files causing the error.)
I'll try to capture a crash dump next time.
- Wil
VA_X.dll file version 10.3.1530.0 built 2006.07.08
Licensed to:
VA X: [email protected] (17-user license) Support ends 2006.12.02
VAOpsWin.dll version 1.3.3.4
VATE.dll version 1.0.5.7
DevEnv.exe version 7.10.3077.0
msenv.dll version 7.10.3077.0
Font: Courier New 13(Pixels)
Comctl32.dll version 5.82.2900.2180
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;
d:\\views\\snaplibs\\h2o\\lib\\boost_1_33_1;
d:\\views\\snaplibs\\h2o\\lib\\mcl\\include;
Library Includes:
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;
z:\\h2o\\src\\Projects;
Other Includes:
|
|
|
|
wilstark
Junior Member
USA
22 Posts |
Posted - Jul 17 2006 : 2:44:25 PM
|
I've reproduced the issue exactly as just posted, and have created a minidump. Send email if you would like it. Also, I could try it again turning on VA-X's logging just before if you mention how this is done. (I tried checking the 'Enable Logging' box under 'Performance' just after the GUI becomes responsive after loading the .sln but before opening the file that caused the crash, but it did not crash that time.)
- Wil |
|
|
| |
Topic |
|
Pure virtual fn call/crash using 1526
