this was the third time that VS.NET 2003 crashed on startup since the installation of VAX 1235. I tried to attach a new instance of VS.NET 2003 as the debugger but that one crashed in the same way:
After killing both VS.NET instances and starting a new one everything worked fine.
In all crash cases I started VS.NET by double clicking on a sln file. The forth crash was the debug attach. I had no crash when starting VS.NET from the Start menu. So maybe there are some timing conditions of VS.NET startup, VAX initialization and a "concurrently" opening solution?
Now I had the crash on VS.NET startup from the start menu - no sln-double-click.
VS.NET says its va_x.dll ModVer 10.0.1237.0 Offset 0019f9f5
I attached with windbg. One thread was at
SharedUserData!SystemCallStub+0x4 WARNING: Stack unwind information not available. Following frames may be wrong. ntdll!NtWaitForSingleObject+0xc ntdll!RtlEnterCriticalSection+0x44 va_x!MigrateDevColor+0xb8616 va_x!MigrateDevColor+0xa1ce7 kernel32!FlsSetValue+0x779
another at
SharedUserData!SystemCallStub+0x4 WARNING: Stack unwind information not available. Following frames may be wrong. ntdll!NtDelayExecution+0xc va_x+0x759d va_x!MigrateDevColor+0xb85fc va_x!MigrateDevColor+0xa1ce7 kernel32!FlsSetValue+0x779
another at
SharedUserData!SystemCallStub+0x4 WARNING: Stack unwind information not available. Following frames may be wrong. ntdll!NtDelayExecution+0xc kernel32!Sleep+0xb va_x!MigrateDevColor+0xb85fc va_x!MigrateDevColor+0xa1ce7 kernel32!FlsSetValue+0x779
The next start went OK. Seems like some timeing issue. I have a dual XEON machine with hyperthreading so the OS sees 4 CPUs - maybe it is some multithreading issue...
Topic Locked
Posted - May 12 2004 : 02:10:32 AM
