T O P I C R E V I E W |
Michal Puczynski |
Posted - Jun 20 2006 : 08:40:00 AM I had a nice full-day debug session with VC+VA then ended with "VA loaded but dormant". It happened after loading VC from JIT in a reaction to access violation caused by tested application. I tried to get rid of it and get back with licensed version but I failed, neither re-login nor restart helped. VA claimed the license expired, so I had to look into the e-mail and reinsert the key.
How to reproduce: - run VC with VA instance - run APP that causes problem - in the JIT window answer to run new VC instance * it loads, VA shows the message and disables functionality.... |
14 L A T E S T R E P L I E S (Newest First) |
support |
Posted - Jul 21 2006 : 12:49:38 AM Update from Michael who no longer has the JIT problem:
"It seems that once I entered the license [for VA X] for the second time, expiration in JIT is not reported anymore...." |
Michal Puczynski |
Posted - Jul 06 2006 : 11:28:01 AM Oh, your are right, SPAM filter redirected it to /dev/null. Got it now. |
support |
Posted - Jun 28 2006 : 11:51:55 AM Michal: We tried sending several emails to you via the address in your profile. You apparently have not received them.
Can you check the address in your profile and/or check your spam filter? Another option is to send a message to [email protected] referencing this topic. |
Michal Puczynski |
Posted - Jun 28 2006 : 03:06:00 AM Exactly the one, but it happened just once to me and I see no connection with licensing issue. Normally more than one instance runs smoothly. |
bugfix |
Posted - Jun 27 2006 : 09:46:19 AM This one?:) No idea how to reproduce it, but it happend when starting a 2nd IDE instance. After 2 mins I gave up and killed the IDE.
-bugfix |
Michal Puczynski |
Posted - Jun 27 2006 : 09:35:28 AM Plain installation of visual c++ standard + visual assist. No kernel debugger installed. |
feline |
Posted - Jun 26 2006 : 4:21:10 PM i am going to have to ask support, since i really do not know to be honest.
do you have any sort of system debugger installed? that should not be a problem, but maybe it is a factor. SoftICE is the standard example people report having problems with. |
Michal Puczynski |
Posted - Jun 26 2006 : 04:45:31 AM Normally I have no problems running more instances of studio with VA active. But on 1522 it happened once that I got something like "waiting for another VA instance to release DB". I just tried 3 instances, no problem. I am with other colleagues in a network; 9 more use the same license as I do, one more VA is running as trial.
At the moment I am using:
VA_X.dll file version 10.3.1524.0 built 2006.06.16 Licensed to: VA X: [email protected] (10-user license) Support ends 2006.12.22 VAOpsWin.dll version 1.3.3.3 VATE.dll version 1.0.5.7 DevEnv.exe version 7.10.3077.0 msenv.dll version 7.10.3077.0 Font: Courier 13(Pixels) Comctl32.dll version 5.82.2900.2180 Windows XP 5.1 Build 2600 Service Pack 2 2 processors
|
feline |
Posted - Jun 24 2006 : 10:38:05 AM *ah* thank you for that Bugfix. it is amazing the number of things i do not know
i never do that, since i am so used to requiring either the output window or break points to check up on what my program is doing.
having done that i am getting a second instance of the IDE launched to debug the process, but no license warnings or anything else. VA is active and happy in both the original IDE, where i was editing the code, and in the new IDE, where i said i wanted to debug the code.
Michal which version of VA are you using? when does your current licence expire? this is in VA options -> about what happens if you simply launch two or three copies of the IDE manually? are you on a local network with other computers that are also using VA? this should produce a different response, so this is an unlikely answer. |
bugfix |
Posted - Jun 24 2006 : 10:24:44 AM feline, you must run that app outside of IDE. |
feline |
Posted - Jun 24 2006 : 10:21:54 AM i am starting to see why what you describe is not familiar to me. when i try this in a C++ command line program i get "break", "continue" or "ignore" as options, and that is it. none of these bring up a second IDE.
i am getting the same effect in a MFC program.
i will ask support about this, since you should not be having this problem. |
Michal Puczynski |
Posted - Jun 21 2006 : 02:55:52 AM It does not matter what application I am running and what kind of application is causing Just In Time window to appear. The fact is that if I choose to use new Visual C++ 2003 instance for the debugging purpose, the VA that runs together with it claims the license has expired. Regarding triggering the JIT, by default VC install itself to catch application problems so it replaces system's Dr.Watson. So, any app causing problem is useful. *(int*)NULL = 4; should be OK. * the IDE is VC++ 2003 * VA is either 1522, 1524 or 1446, all have the same problem * C++ (but that does not matter as app is external) * I am not trying to write a plugin. |
jpizzi |
Posted - Jun 20 2006 : 8:51:09 PM JIT = Just In Time
Michal: For simplicity of finding a problem that invokes JIT, what problem was it that your code had? Was it a debug or release build? Since JIT was invoked, I presume that you were running the app outside the IDE? |
feline |
Posted - Jun 20 2006 : 5:00:16 PM assume for the moment i have no idea what JIT is, or how to trigger it...
* which IDE are you using? * which version of VA are you using? * what programming language are you using?
are you trying to write an IDE plugin? |