>FWIW, VFP C++ Compiler has a Application Debug option that creates a log line before and after each code line runs. If a variable is set by the line of code, the variable with newly set value is also logged. My experience: while pursuing a new issue, this feature unexpectedly allowed detection of a decade-old bug that had been worked around because nobody could replicate it. If it's happening at the start of your app, sending a VFPC++ exe with Application Debug enabled should provide lots of useful info leading up to the fault.
>

22 years ago I would have paid a lot for embolded - had to create my own fwk to identify slow parts in C as vfp coverage profiler piping to file on each line created Heisenberg effects...
Pretty certain you can either define what function to call or call a hook or some similar pattern ?

regards
thomas