LV Stack Trace Log File

[Raeff]

Hi everyone,

Problem:

Our LV (14 SP1)  built exe works perfectly on our test HW, however at our customer's (Runtime Engine) on the same HW it freezes without any error message.

What I'm looking for:

For remote debugging purposes it would be very helpful to get a "Stack trace history log file", such that the customer can send us this file and we know which code has been executed and which not.

Something similar to 'printStackTrace' in Java.

Is it possible to get the stack trace in LV RTE? Or is there a log file with this information?

Thankful for any suggestions on how to solve this problem.

I am looking for something like this but also if there was no (internal LV) error at all: http://forums.ni.com/t5/LabVIEW/Crash-log-storage-location-for-EXEs/td-p/2098736

What I want is similar to the original question of this post: http://forums.ni.com/t5/LabVIEW/LabView-Stack-Trace-or-Call-Stack-Tracing/m-p/478424/highlight/true#...

however, this question was not answered as the asker actually wanted to trace an event.

I know about Remotely Debugging Executables in LabVIEW as described here: http://digital.ni.com/public.nsf/allkb/8DA679805915DE40862572D5007B2F70

however this requires Network connection, which not all of our customers can provide due to security restrictions.

I also looked into the LabVIEW Datalogging and Supervisory Control (DSC) Module, but actually I do not want to log data but only the call chain/stack trace.

If there is no built in way in the LV RTE do you have tips on how to implement this degub stack trace logging?

Thanks a lot.

Best

Raeff