02-24-2009 07:01 AM
When LabVIEW 8.6 launches it says I have some vi's not linked to any library. It asks if I want them linked to the class they should belong to.
When I do I get a crash and the error log below.
####
#Date: Tue, Feb 24, 2009 7:38:57 AM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.6
#AppKind: FDS
#AppModDate: 06/26/2008 01:25 GMT
c:\builds\penguin\labview\branches\Saturn\dev\source\objmgr\OMUDClassLinker.cpp(3196) : DAbort: Should never have already existing class when patching the thing that is loading the class!
$Id: //labview/branches/Saturn/dev/source/objmgr/OMUDClassLinker.cpp#68 $
0x00E98AAA - LabVIEW <unknown> + 0
0x00E99AA3 - LabVIEW <unknown> + 0
0x00D3D553 - LabVIEW <unknown> + 0
0x0107753D - LabVIEW <unknown> + 0
0x01077F8F - LabVIEW <unknown> + 0
0x01078823 - LabVIEW <unknown> + 0
0x010788CE - LabVIEW <unknown> + 0
0x005FABA6 - LabVIEW <unknown> + 0
0x00A8FAE7 - LabVIEW <unknown> + 0
0x00A88F3C - LabVIEW <unknown> + 0
0x00A891D9 - LabVIEW <unknown> + 0
0x00A9040E - LabVIEW <unknown> + 0
0x00A90514 - LabVIEW <unknown> + 0
0x00A8CD7F - LabVIEW <unknown> + 0
0x00A8CE3F - LabVIEW <unknown> + 0
0x011461FE - LabVIEW <unknown> + 0
0x010F52E0 - LabVIEW <unknown> + 0
0x010F54FC - LabVIEW <unknown> + 0
0x0110FD6A - LabVIEW <unknown> + 0
0x0112A211 - LabVIEW <unknown> + 0
0x0112AD04 - LabVIEW <unknown> + 0
0x0109BB64 - LabVIEW <unknown> + 0
0x01110B81 - LabVIEW <unknown> + 0
0x011191CA - LabVIEW <unknown> + 0
0x01119D57 - LabVIEW <unknown> + 0
0x0111A110 - LabVIEW <unknown> + 0
0x0111AD41 - LabVIEW <unknown> + 0
0x0111AF2A - LabVIEW <unknown> + 0
0x0111B3AA - LabVIEW <unknown> + 0
0x0111B4A8 - LabVIEW <unknown> + 0
0x01080718 - LabVIEW <unknown> + 0
0x01080748 - LabVIEW <unknown> + 0
0x01080748 - LabVIEW <unknown> + 0
0x010807C5 - LabVIEW <unknown> + 0
0x010964B6 - LabVIEW <unknown> + 0
0x0109943D - LabVIEW <unknown> + 0
02-25-2009 01:20 PM
Hi Jamey,
I'm sorry to hear that LabVIEW has been crashing. This was reported to R&D (# 148741) for further investigation. To determine the cause, I have a few questions.
1. What operating system are you running?
2. If you choose not to link the VIs to a class, what is the result?
3. Did this begin recently, and were any changes made to your system lately?
I would suggest repairing LabVIEW. You can do so by following these steps:
1. Open the Windows Control Panel.
2. Choose Add or Remove Programs.
3. Select National Instruments Software and click Change.
4. Select NI LabVIEW 8.6 and click Repair.
5. Follow the steps to complete the repair process.
You will likely be prompted for the installation disks when repairing the software.
Please do let me know if that resolves the issue.
02-25-2009 01:38 PM
I don't think I have to repair the installation. It is LabVIEW 8.6 not 8.6.1. I think I understand what I did to cause the problem. It's something that reflects some of my mindset when I program. I do some up front design and planning, but when I start to program, other things come out and I make changes on the fly as I go.
The sequence of events is this...
1. Create a class
2. Added 4 booleans
3. Created some dynamic vi's by right clicking on the class in the project window. Save the newly created VIs.
4. Delete the booleans from the class definition and add some numbers and strings instead.
5. Do not delete the original dynamic vi's
6. Close LabVIEW and go home.
7. Next morning re-launch the project file and when LabVIEW tries to link the vi's to the class it doesn't know
what to do. So it asks if I want to add, remove or cancel re-linking the original vi's. If you tell it to relink or even cancel, LabVIEW dies.
8. The message: "DAbort: Should never have already existing class when patching the thing that is loading the class!" appears.
Perhaps you should just add a check for an insane object between the CRT and the chair!
Thanks. While I don't like getting crashes, this one I think is understandable.
Jamey