LabVIEW Crash 2015 (Need Conclusion Whether its a Bug)

[PalanivelThiruvenkadam]

As we can give array of delimiter input  for spreadsheet string to array, assume by mistake the developer leaves any one element with empty string "LabVIEW End up with crash report"

Though its developer mistake, LabVIEW should Provide error instead of crash

[billko]

It happens with LV 2014 as well.  Because this is an operating system exception and not a LabVIEW error, things get murky.  Apparently LabVIEW is calling some dll and it returns an error in this situation.  Who knows if LV is using the dll incorrectly or that the dll itself has a bug in it.

[PalanivelThiruvenkadam]

As it's an known error LabVIEW should be capable of handling even it's an OS exception or problem with dll or problem with handling dll..
It should throw an error message instead of crash report..

[billko]

---

@PalanivelThiruvenkadam wrote:
As it's an known error LabVIEW should be capable of handling even it's an OS exception or problem with dll or problem with handling dll..
It should throw an error message instead of crash report..

---

Well... LabVIEW is handling it.  It actually generated a report that you can send to NI, right?  And anyway, why would you want to continue running an application that has already tried to access memory hat the operating system believes does not belong to it?  You don't recover from an OS exception.  You exit gracefully as possible when it happens.