LV errors or crashes, show location e.g. call chain.

[FermWorks]

Show where a LV error like "There is not enough memory to perform this operation" is coming from, either in the text of the error dialog (call chain and which node) or in log file, and (if using LV development not runtime) open & highlight the problem location. This is an example of an error that can't be caught by our LV code and doesn't crash LV to produce a crash log.

[AristosQueue (NI)]

We generally show the call chain everywhere that we can. In the case of "not enough memory", I know that this has come up in the past that we can't allocate enough memory to show the call chain because we are out of memory and cannot build the string. If you have a particular piece of example code where we aren't showing the call chain, we might be able to fix that spot up.

[fabric]

One could imagine that since you are about to crash anyway, that stealing back some already-allocated memory to allow a better error description might be better in the long run!

[GregSands]

Or retain enough memory to always be able to build a call chain - not many user programs will fail for the want of 1KB.

[AristosQueue (NI)]

> Or retain enough memory to always be able to build a call chain -

> not many user programs will fail for the want of 1KB.

I've seen this on RT systems which, yes, do run that close to the edge of memory. I don't think I've seen it on desktop for many years.

[Darren]

Any idea that has received less than 6 kudos within 6 years after posting will be automatically declined.