LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Fatal error: protocolsup.cpp

Hi,
This problem is just happened to me. This is the log file.
First it happened when I set the breakpoint. After I found this forum, I tried to remove the breakpoint but the LabVIEW still crashes. It's so dissapointed.
It happens at line 3244. From now on, I cannot run the code anymore T_T.
 
####
#Date: Mon, Apr 14, 2008 3:44:16 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.5
#AppKind: FDS
#AppModDate: 07/25/2007 02:07 GMT
 
c:\builds\penguin\labview\branches\Jupiter\dev\source\server\protocolsupp.cpp(3244) : DAbort: MakeSyncCallEx: No available slots for opcodesent:77 27=kOpSetVIState, waiting for 1132=kOpSetInstrStateAck
sent:78 27=kOpSetVIState, waiting for 1132=kOpSetInst
$Id: //labview/branches/Jupiter/dev/source/server/protocolsupp.cpp#57 $
0x00F4C898 - LabVIEW <unknown> + 0
0x00AE5096 - LabVIEW <unknown> + 0
0x00874723 - LabVIEW <unknown> + 0
0x005E1C4B - LabVIEW <unknown> + 0
0x0049C139 - LabVIEW <unknown> + 0
0x0049A981 - LabVIEW <unknown> + 0
0x0049C1EC - LabVIEW <unknown> + 0
0x00405678 - LabVIEW <unknown> + 0
0x0040599B - LabVIEW <unknown> + 0
0x0041EDB0 - LabVIEW <unknown> + 0
0x0053EC85 - LabVIEW <unknown> + 0
0x00F4E9C6 - LabVIEW <unknown> + 0
0x00F4C069 - LabVIEW <unknown> + 0
0x00F4C898 - LabVIEW <unknown> + 0
0x00AE5096 - LabVIEW <unknown> + 0
0x00874723 - LabVIEW <unknown> + 0
0x005E1C4B - LabVIEW <unknown> + 0
0x0049C139 - LabVIEW <unknown> + 0
0x0049A981 - LabVIEW <unknown> + 0
0x0049C1EC - LabVIEW <unknown> + 0
0x00405678 - LabVIEW <unknown> + 0
0x0040599B - LabVIEW <unknown> + 0
0x0041EDB0 - LabVIEW <unknown> + 0
0x0053EC85 - LabVIEW <unknown> + 0
0x00F4E9C6 - LabVIEW <unknown> + 0
0x00F4C069 - LabVIEW <unknown> + 0
0x00F4C898 - LabVIEW <unknown> + 0
0x00AE5096 - LabVIEW <unknown> + 0
0x00874723 - LabVIEW <unknown> + 0
0x005E1C4B - LabVIEW <unknown> + 0
0x0049C139 - LabVIEW <unknown> + 0
0x0049A981 - LabVIEW <unknown> + 0
0x0049C1EC - LabVIEW <unknown> + 0
0x00405678 - LabVIEW <unknown> + 0
0x0040599B - LabVIEW <unknown> + 0


Message Edited by THANG NGUYEN on 04-14-2008 03:57 PM
0 Kudos
Message 31 of 34
(910 Views)
Something I just found out (a year and 4 months after I first asked about this problem). I am using LV-realtime talking to LV-fpga on a PXI chassis. I made the mistake of putting a breakpoint in the RT code and got the problem back. It wouldn't go away until I shut down and restarted the PXI chassis.

So you might try rebooting to see if the problem goes away.

Still mighty anoying though.

Chuck
0 Kudos
Message 32 of 34
(899 Views)
@cgantz2000: Thank you, I restarted and it runs now. It's sweet ^__^.
0 Kudos
Message 33 of 34
(896 Views)
Yes, i am experiencing the same problem now. I am using RT8.2.1. When this happened, I really don't know what trigged the problem. Now I think it should be the Breakpoints sitting in the blocks because I have set some breakpoints to debug the program. but anyone have some idea how to solve it. We still need the breakpoints to debug problem, don't we?

0 Kudos
Message 34 of 34
(843 Views)