The last time you ran LabVIEW, an internal error or crash occurred at source/typedesc/DSTM.cpp, line 211.

[wbdoyle]

Nickled and dimed once again by obscure errors. This is LabVIEW 10.0.1 on Redhat EL 5.5 32-bit.

I removed an enum from the project that is also used in a typedef control cluster. Since many VIs use this typedef I have to go to each VI and save in order to remove the phantom dependencies (i.e. popup can't find enum ctl when opening VIs). In the process of opening every VI and saving LabVIew is crashing on me reliably but not everytime just after I press cancel when it tries to find the enum ctl.

Here are the errors. Sometimes the address is null....I believe LabVIEW src code should check for null/bad pointers but does not in this case.

GenNAryOp_ArrayBase : naryop, setdef? ninp=1
Compiler error.  Report this problem to National Instruments Tech Support.

copy cvt str/pict/tag, csrc=0xFF
Compiler error.  Report this problem to National Instruments Tech Support.

copy cvt, csrc=0x21
Compiler error.  Report this problem to National Instruments Tech Support.

copy cvt bool, csrc=0x30
Compiler error.  Report this problem to National Instruments Tech Support.

copy cvt str/pict/tag, csrc=0xA
Compiler error.  Report this problem to National Instruments Tech Support.

copy cvt, csrc=0x50

LabVIEW caught fatal signal
10.0.1 - Received SIGSEGV
Reason: address not mapped to object
Attempt to reference address: 0x0xffffffff

Upon reopening LV I see this.

The last time you ran LabVIEW, an internal error or crash occurred at source/typedesc/DSTM.cpp, line 211.

[Blizzard]

Hello wbdoyle,

I'm sorry you are seeing that error. Did you close and save the type def that included the enum? This should prevent you from having to go through and save each VI that includes the type def.  Are you using the System Exec VI? Also, are you performing any data acquisition with the VI you are referencing? The error you are seeing indicates that the LV compiler isn't handling something in your VI and I want to pinpoint exactly what is happening.

Thanks!

Regards,

Anna L