| Author |
 Topic  |
|
|
ptr727
Senior Member
31 Posts |
 Posted - Jun 13 2004 : 4:33:25 PM
|
This problem has been going on forever and I am at the point of giving up on VAX :(
When opening a project (not the IDE, the project) VS 7.1 would crash in va_x.dll.
Unfortuanltey this is not 100% reproducable, but happens at least a few times a day for me.
What can I do to the dev team get rid of this problem? |
|
|
Uniwares
Tomato Guru
Portugal
2321 Posts |
Posted - Jun 13 2004 : 4:59:26 PM
|
send in a crash dump, a list of loaded modules, plug-ins, anything that might be "different" from usual configurations. Enable logging in the VAX options before you load a project and send in the VAX log.
That should do the trick. |
 |
|
|
ptr727
Senior Member
31 Posts |
Posted - Jun 13 2004 : 5:22:11 PM
|
Uniwares:
- The problem is not reproducable on demand, and VA (seems) to turn logging off after an IDE restart. I may forget to turn logging on every time. How can I keep logging enabled all the time?
- msdev crashes but I have not been able to debug the crash, i.e. attach with windbg or another msdev. A crash report is submitted to M$, but there is no dump file. Any other ideas on how to get a dump file?
|
|
|
|
ptr727
Senior Member
31 Posts |
Posted - Jun 13 2004 : 7:24:48 PM
|
Hmm, I am now running msdev from windbg, but it seams VAX does not like that:
"For security purposes, this program will not run while system debuggers are active. Please remove or disable the system debugger before trying to run this program again." Searches on google points to VAX causing this. :( |
|
|
|
ptr727
Senior Member
31 Posts |
Posted - Jun 13 2004 : 7:49:48 PM
|
Since VAX does not like it when windbg runs msdev, I used adplus to attach after launching, and I mananaged to get a 2nd chance access violation with VAX on the stack. But, I forgot to turn logging on.
Now, how do I send support a 300MB dump file?
Here is an extract:
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
FAULTING_IP:
VA_X!DllCanUnloadNow+3e763
1eea0e26 3b7308 cmp esi,[ebx+0x8]
EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff)
ExceptionAddress: 1eea0e26 (VA_X!DllCanUnloadNow+0x0003e763)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000027
Attempt to read from address 00000027
DEFAULT_BUCKET_ID: APPLICATION_FAULT
PROCESS_NAME: devenv.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
READ_ADDRESS: 00000027
BUGCHECK_STR: ACCESS_VIOLATION
THREAD_ATTRIBUTES:
LAST_CONTROL_TRANSFER: from 00000000 to 1eea0e26
STACK_TEXT:
1ef2960c 00000000 01762348 0176395c 0176395c VA_X!DllCanUnloadNow+0x3e763
FOLLOWUP_IP:
VA_X!DllCanUnloadNow+3e763
1eea0e26 3b7308 cmp esi,[ebx+0x8]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: VA_X!DllCanUnloadNow+3e763
MODULE_NAME: VA_X
IMAGE_NAME: VA_X.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 40bdffd1
STACK_COMMAND: .ecxr ; kb
BUCKET_ID: ACCESS_VIOLATION_VA_X!DllCanUnloadNow+3e763
Followup: MachineOwner
---------
------------------------------
VA_X.dll file version 10.0.1239.0
Licensed to:
VA X:
VA.NET 7.1: [email protected] (1-user license)
VAOpsWin.dll version 1.0.0.44
DevEnv.exe version 7.10.3077.0
msenv.dll version 7.10.3077.0
Font: Courier New 13(Pixels)
Comctl32.dll version 5.82.2800.1106
WindowsNT 5.1 Build 2600 Service Pack 1
4 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;
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;
Other Includes:
|
|
|
|
ptr727
Senior Member
31 Posts |
Posted - Jun 13 2004 : 8:42:56 PM
|
| And now I have a dump and VA logs, just need to know where to send them. |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Jun 15 2004 : 12:33:36 PM
|
300M is a bit to big for email. Just looked at the docs for adplus and I see it can do "MiniDumps" ie not full memory dumps "FullDump". But I cannot find the option in the quick info.
Anybody have a quick answer for this?
Once the exception happens, you should be able to click "More info/Debug", to attach to the process with vs.net. You can save a MiniDump in "Debug/Save dump as...".
Can you zip the logs and send to [email protected]?
|
Whole Tomato Software, Inc. |
|
|
|
ptr727
Senior Member
31 Posts |
Posted - Jun 17 2004 : 08:54:05 AM
|
Support:
- Note that a minidump is not necessarily a small dump (see MSDN or WinDbg help).
- Dumps generated from within VS are not as complete as the dumps generated by adplus.
I mailed my compressed logs (5MB) to support.
I am still waiting to hear how to send you (FTP perhaps?) my compressed dumps (240MB). |
|
|
|
lethalhamster
New Member
9 Posts |
Posted - Jun 17 2004 : 4:18:31 PM
|
The easiest way to get a crash dump from when VS.NET crashes is to copy the one that Watson generates (that's the "please tell microsoft about the problem - send / don't send" dialog that comes up after a crash).
If you look in your temp folder (usually C:\\Documents and Settings\\???\\Local Settings\\Temp) when Watson is up you'll see a .dmp file. You can't copy it while 'drwin.exe' has a hold on it, so kill that off in the processes tab of task manager. Then copy the .dmp file from your temp directory and send it in, they tend to be no more than a few hundred KB.
|
-\rJohn C |
|
|
|
ptr727
Senior Member
31 Posts |
Posted - Jun 18 2004 : 8:59:41 PM
|
lethalhamster:
Unfortuantely there are no dumps on the system after submitting crashes to Microsoft.
But, I created very small dumps (using windbg .dump /m) from my very large dumps.
I will email these and my logs to support and hope it helps resolve this problem. |
|
|
|
lethalhamster
New Member
9 Posts |
Posted - Jun 19 2004 : 11:22:45 AM
|
| Pieter: That's why you have to kill 'drwin.exe' off from task manager - otherwise it deletes the dump file after it sends it to Microsoft. |
-\rJohn C |
|
|
| |
Topic |
|
Topic Locked
