Has anyone ever heard of a way to get information as to why a LV 7.0 (or earlier) application is hung?

[Ben]

What I would really like, is a crash dump or an error message telling me why the event structure is not responding to user events.

FYI
The application has lots of log files and error logging that shows that every thing was fine up until Saturday night at midnight. Six seconds after midnight most file activity stopped.

Although there are some back ground processes that still seem to be running (Time and date is still updating and at least one file is still being updated regularly). The application has error logging built in, but unfortunately the error log file is one of the files that stopped getting updated!

So, if you have heard of this being done, please
throw me a lead so I can run with it.

Thank you,

Ben

[chrisger]

hi ben

i once had an app with lots of dynamic stuff. i wanted to get some information about the time some vis have been called. so i put an timestamp indicator on the fp of each vi and wrote the current time to that indicator when the vi executed. all indicators had the same label. i then ran a vi in the back, polling the value of the timestamp indicator of all vis in memory using the GetControlValue-property (can be done purely generic!). i wrote the vis name and the timestamp in a log file, so i had a log of the last time all the vis have been executed.
maybe thats an idea.

best regards
chris

[Ben]

Interesting idea!

Unfortunately;

1)the EXE is hung as I write!
2)log file writing is also hung.

Thank you Chris.

I would still like to hear more ideas if anyone else would like to share.

Ben

[chrisger]

hi

well, there's another one:

you talked about user events: each time you fire the events you could write to a log file firedevents.log. in your event-cases you write to another log file catchedevents.log all information you can get from the event parameters. when there's a gap between fired and catched events you know the event that hasn't been catched.

best regards
chris

[Ben]

Hi Chris,

This an interesting approach. It would be rather complicated to implement in a large application after the fact, but could be implemented using a round robin buffer so that long running apps don't become memory hogs.

Keep those ideas coming!

Ben

P.S. Please post new ideas as new answers. I feel that every unique approach is worthy of stars.

When brainstroming all ideas are good!