Does anyone know what mFlags are or what they mean?

[Matt_AM]

Hey Fancy Folk,

Does anyone know what mFlags are or what they mean?  From my current understanding, they are used by the NI R&D team to figure stuff out when things fail, and I believe they aren't public knowledge as to what the mFlags mean.  

Reason I'm asking is because I'm using an Linux RT system and I get a message that is saying that the a VI is not executable with error 0x3EB.  After doing some digging for the logs, I came across folder location "/var/local/natinst/log" on the RT system and found the lvlog[date/time stamp] files and I see that there are LINKOBJ_BROKEN errors, so I know where I can start looking to fix the code. 

However, I also see the mFlags = 18976 and 16896 value under the error and I was wondering if anyone knew what they meant.  Like I said previously, I believe they are used for the NI R&D team, so I am not expecting someone to know.

Matt

[Jacobson]

I'm guessing those are the same flags you'd see in Heap Peek. I've never found them to be particularly helpful because the flags will just say that the VI is bad or it can't compile which is basically what the error log is telling you.

These flags aren't just used for debugging they're basically just some bitfields properties of the internal VI object in LabVIEW. I'm pretty sure the "m" in mFlags is just an older way to denote that the variable is a member.