crash reporting

[GlennPierce]

Hi I would like to generate a simple crash report when my program cause or
general protection fault or access violations which could then be automatically sent to me ?

Is there anyway in labwindows that I can generate a mini dump or stack trace on program crashes ?

Thanks for any advice.

Glenn

[AdnanZ]

Hi Glenn,

I hope you are doing well today! We don't have a report generation tool in LabWindows/CVI.

LabWindows/CVI user protection allows the compiler to monitor all types of pointer manipulations in your code and store data structures internally for each type. At run time, LabWindows/CVI dynamically watches your pointer manipulations and informs you of illegal accesses.  It does the same actions for simple out-of-bounds indexing of statically declared arrays and more complex series of dynamic allocations with malloc, calloc, and so on.

You can configure LabWindows/CVI to display a run-time error dialog box and suspend execution when an NI library function reports an error. To enable this type of debugging, select Run>>Break on>>Library Errors functions or use the Utility Library SetBreakOnLibraryErrors/GetBreakOnLibraryErrors functions. You also can work around user protection errors flagged by LabWindows/CVI by using the SetBreakOnProtectionErrors/GetBreakOnProtectionErrors functions. Normally, you apply these functions around a small section of code as a workaround to some pointer problems you have coded into your program.

Here are some useful links:
how to handle run-time errors in CVI
Run-time error checking: a personal solution