LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Fatal error splitpanels.cpp line 1148

I'm using LV 8.2.1 and I'm getting a fatal error.  I've tried re-loacting my code in order to purge it, but to no avail.

 

The error message says "SplitPanels.cpp" Fatal error line 1148....

 

Any idea what's going on here?


It happens when I receive a double-click on one VI (located in a sub-panel of the main VI), relay a message to the main VI to replace the VI with another in the sub-panel.

 

There's a singlesequence of code which bombs LV.  The same frame of my State maching can be called via other means without bombing, so there must be something in the background.....

 

Shane.

0 Kudos
Message 1 of 7
(3,374 Views)

 Hello Shane

 

Here is the link to a knowledgebase that deals with the same error.

http://digital.ni.com/public.nsf/allkb/FB79ED8B6D07257B86256E93006E31FA?OpenDocument 

 

Do you find a solution with this link?

let me know

 

Daniela 

0 Kudos
Message 2 of 7
(3,353 Views)

Unfortunately, I haven't found what I'm looking for there.

 

 I'm not getting an unhandled error, I'm getting a Fatal error.  I'm crashing LabVIEW.

 

 Fatal Error

 

I've simply disabled the particular part of code leading to this.....

 

It also crashes in 8.5.1.

 

Shane.

Message Edited by Intaris on 08-27-2008 09:02 AM
0 Kudos
Message 3 of 7
(3,349 Views)

 Hello Shane

 

in 8.5.1 is it the very same error message?

could you please upload this message too?

 

because this fatal error was a bug in 8.2 and was fixed in 8.5.1

below you find a table with all bugs fixed in 8.5.1

 

http://zone.ni.com/devzone/cda/tut/p/id/6210

 

bug Number: 42F97CIQ

 

Daniela 

0 Kudos
Message 4 of 7
(3,341 Views)

I could have sworn I got a similar message under 8.5.1 when I tested it yesterday, but upon checking now, it ran fine.

 

When I restart LabVIEW though, I get a message that the last instance generated an error in "SupC.cpp" Line 1215.

 

Hmm, maybe it's already a (half-)fixed bug.  I'm not dragging strings anywhere, so I don't know if the bug you listed is directly applicable, but perhaps my problem is a side-effect of that fix.

 

I've sent an email to NI on the subject.

 

Unfortunately the customer insists on 8.2.  I'll just have to do without the functionality.  It was just the icing on the cake, nothing which would endanger a project.

 

Shane.

0 Kudos
Message 5 of 7
(3,336 Views)

Shane,

 

who are you in contact with through e-mail?

 

I'd like to know to check the case because I'm from NI too (Switzerland). 

 

Daniela 

0 Kudos
Message 6 of 7
(3,319 Views)

I used the web formula for contacting NI by email, and I haven't got anything beyond the autimatic reply, so I don't have the contact details of anyone yet.


The onky piece of identifying information I have is the reference number : Reference#9378-KHB417.

 

Should I contact NI Switzerland when I want to report something?  I've never reported many bugs, so maybe I'm doing it wrong   :smileysad:

 

Shane.

0 Kudos
Message 7 of 7
(3,315 Views)