| T O P I C R E V I E W |
| hwatson |
Posted - Oct 10 2006 : 1:42:20 PM
I got the following crash when attempting to open a solution. I don't know if it's related to VAX or not, but VAX is in the callstack.
ntdll.dll!_DbgBreakPoint@0()
ntdll.dll!_RtlApplicationVerifierStop@40() + 0x160
ntdll.dll!_RtlpDebugPageHeapPointerFromHandle@4() + 0x74
ntdll.dll!_RtlpDebugPageHeapFree@12() + 0x24
ntdll.dll!_RtlDebugFreeHeap@12() + 0x2c
ntdll.dll!_RtlFreeHeapSlowly@12() + 0x23d19
ntdll.dll!_RtlFreeHeap@12() + 0x16470
msenv.dll!50045d71()
msenv.dll!502a2a7e()
msenv.dll!500cad30()
msenv.dll!5010d785()
VaPkg.dll!4efd781f()
VaPkg.dll!4efd6efa()
VA_X.dll!1ed6c059()
ntdll.dll!_RtlpAllocateFromHeapLookaside@4() + 0x31
ntdll.dll!_RtlpAllocateFromHeapLookaside@4() + 0x31
00161378()
ntdll.dll!_RtlpAllocateFromHeapLookaside@4() + 0x31
Here's my environment info:
VA_X.dll file version 10.3.1538.0 built 2006.10.06
VAOpsWin.dll version 1.3.3.6
VATE.dll version 1.0.5.8
DevEnv.exe version 7.10.3077.0
msenv.dll version 2.0.3529.0
Font: Courier New 13(Pixels)
Comctl32.dll version 5.82.2900.2180
Windows XP 5.1 Build 2600 Service Pack 2
2 processors |
| 5 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Oct 12 2006 : 6:46:59 PM
Fixed in build 1539. |
| sean |
Posted - Oct 11 2006 : 2:41:57 PM
Thanks for the callstack - case=2974. |
| sean |
Posted - Oct 11 2006 : 12:34:37 PM
This callstack does point to VA - it looks like it might have been calling on an IDE service that crashed. We should be able to catch the exception if we're able to identify the calls. |
| hwatson |
Posted - Oct 11 2006 : 12:28:04 PM
This only happened once. I closed Visual Studio and then opened the solution again. It worked fine, with the NCB intact.
I realize this callstack in and of itself is not very useful. I posted it in case anyone else has experienced similar behavior. |
| feline |
Posted - Oct 10 2006 : 3:38:26 PM
is this solution specific?
can you try deleting the NCB file in the base directory of the solution and try again? I have seen VS2003 crash when loading a solution due to a corrupt NCB file.
has this only just started happening? if deleting the NCB file does not help do you know what might have triggered this? |
