| Author |
 Topic  |
|
|
SaloS
Junior Member
23 Posts |
 Posted - Nov 24 2006 : 05:49:16 AM
|
I had and attempt to debug VANetObj20.dll while I loaded one solution. I see following picture
some information that probably can be helpful
1) Solution has 22 projects some of the in C#, some of them in native C++, some in managed C++
2) When I opened solution I have no any generated files (it was clear version from TFS)
3) Some of projects have dependencies to another projects (some C# projects depend on another C# project and use #using on it)
4) I have solution with the same names which VA already parsed and without any errors. (I open first time branched version of solution and got this error). |
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Nov 24 2006 : 12:05:13 PM
|
Can you look for the file "errors.log" please. This should be in one of these two directories:
C:\\Program Files\\Visual Assist X\\vc7\C:\\Program Files\\Visual Assist X\\vc8\
the directory will depend on the IDE you were using.
Does this problem happen every time you load this solution? Or was it a one off problem?
If you can reproduce this the some log files might help as well.
Can you load the IDE, then enable logging:
VA Options -> Performance -> General -> Enable logging
and then load the solution. See here for details of the files produced and how to send us the logs.
http://docs.wholetomato.com?W305
Have you, or anyone else done anything "strange" to this branched solution that might explain why it causes an exception and the other branch does not?
To try and fix this can you try:
VA Options -> Performance -> General -> Rebuild symbol databases
You can also try upgrading to VA 1541 and see if that helps.
http://www.wholetomato.com/downloads/VA_X_Setup1541.exe |
zen is the art of being at one with the two'ness |
 |
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Nov 24 2006 : 12:26:44 PM
|
SaloS if you can reproduce this can you also select debug and produce a call stack in addition to sending in the logs?
You should be able to get a call stack using either:
* New instance of MS CLR debugger 2005
* New instance of Visual Studio 2005 |
zen is the art of being at one with the two'ness |
|
|
|
SaloS
Junior Member
23 Posts |
Posted - Nov 28 2006 : 02:36:46 AM
|
| Unfortunately I cannot reproduce this bug. I don't know why it appeared. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Nov 28 2006 : 3:12:50 PM
|
No crashes is good 
Hopefully you will never have this problem again, but if you do any clues or information you can provide will be gratefully received. |
zen is the art of being at one with the two'ness |
|
|
|
SaloS
Junior Member
23 Posts |
Posted - Dec 14 2006 : 07:38:39 AM
|
I got another similar crash.
 .
I start Visual Studio with my addin and it throws an exception. I attached new Visual Studio had a look where exception is appeared and detach Debug Visual Studio and first Visual Studio. After that I tried to start new instance of Visaul Studio and got a lot of errors similar to above one.
|
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Dec 14 2006 : 11:19:50 AM
|
Do you have any idea what might have changed recently to cause this to start happening again?
Do you have any VB code in your project?
Have you installed, or do you use ActiveSync?
If you are using VS2005 can you use regedit to stop VA from loading before trying to debug this and grab a call stack? See the instructions here:
http://docs.wholetomato.com?W306
If you are using VS2003 there is the registry key:
HKEY_LOCAL_MACHINE \\ SOFTWARE \\ Microsoft \\ VisualStudio \\ 7.1 \\ Addins \\ VAssistNET.Connect \\ LoadBehavior = 3
Toggle this between 0 and 3 to stop VA loading, or to let it load.
|
zen is the art of being at one with the two'ness |
|
|
|
SaloS
Junior Member
23 Posts |
Posted - Dec 15 2006 : 01:48:29 AM
|
| After this messages I saw strange message like "Visual Assist X is waiting for Visual studio flush DB". It was until I close all instances of Visual Studio and start it again. There was one more strange thing, I had devenv.exe process without its window. Probably this is the reason. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Dec 15 2006 : 09:13:38 AM
|
The devenv.exe process without a window is connected to the "Visual Assist X is waiting for Visual studio flush DB" message on the status bar. one cause of this problem should be fixed in VA 1542, which is due in the next few days.
However this should not be related to, or causing this exception. |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
Exception in VANetObj20.dll
