LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Dr. Watson Dr. Watson C0000005 access violation Win NT4.0 and LV7.1

Hi together,

 

I got an error "Dr. Watson C0000005 access violation" after closing my LV application.

LV 7.1 and Windows NT 4.0 SP6a .

 

 Dr Watson

 

Does anybody has an idea?

 

Thanks.

 

 

0 Kudos
Message 1 of 14
(5,328 Views)

I tried also with update to LV 7.1.1. ,   without success.

 

 

0 Kudos
Message 2 of 14
(5,320 Views)

Ich got this error message after disabling Dr Watson.

 

Error Message

 

 

May be this is a LV 7.1 bug?

0 Kudos
Message 3 of 14
(5,310 Views)
What makes you think it's a LabVIEW bug? I'd be more inclined to think it's something within your code. Are you accessing hardware? Are you calling DLLs? Without knowing what your program is doing, you can't say one way or the other.
0 Kudos
Message 4 of 14
(5,301 Views)

Hi,

 

I don't use hardware and no dll is called. I can focus then problem on a part of the program which handles a Systray Icon.

 

http://home.arcor.de/raena2/LabVIEW_Tray_Icon.llb

 

So just using the sample in this llb shows the probelm when closing the application.

0 Kudos
Message 5 of 14
(5,297 Views)

strange thing: if I insert a waiting time between closing the systray icon and exiting the program,

no Dr. Watson and no error message comes up.

 

Does anybody has an idea what the reason could be for this behavior?

0 Kudos
Message 6 of 14
(5,268 Views)

Hi there

 

add a Destroy user event" after the unregister event function for each user event in your code.

 

You are calling external code (axsTrayIcon.ITrayIcon COM-Object), this code may cause the problem.

 

 

Best regards
chris

CL(A)Dly bending G-Force with LabVIEW

famous last words: "oh my god, it is full of stars!"
0 Kudos
Message 7 of 14
(5,255 Views)

Thanks chrisger, but this doesn't help. Same Error Message.

Any other suggestions?

 

 

 

destroy

Message Edited by maximint on 12-12-2008 08:32 AM
0 Kudos
Message 8 of 14
(5,247 Views)
The way you've wired that it won't do anything. UsrEvtRef is only valid inside the event case. When you tunnel it out it like that its value is lost, and is therefore meaningless. I suspect your problem has to do with those external calls that you're making with the systray. Those VIs call Windows DLLs. Why don't you try removing them and see what happens?
0 Kudos
Message 9 of 14
(5,238 Views)

This is wrong. The tunnel of the user event through the event structure is filled with data only in the UserEvent event case,  but this case will not stop the while loop, so the tunnel through the while loop is always NULL.

 

Pass ALL user events created inside "Register Tray Icons Events.vi" to the outside and destroy them after the destroy event registration.

Best regards
chris

CL(A)Dly bending G-Force with LabVIEW

famous last words: "oh my god, it is full of stars!"
0 Kudos
Message 10 of 14
(5,237 Views)