While testing my own code, I've ran into a problem where starting Mach 4 causes a hang in the middle of the "Loading screen elements...".  I'm sure I introduced the problem, but how do I find it?

Ideally I could interrupt the startup and look at the stack trace.  A watchdog timer would be nice on start up that would bailout and give me a stack trace.  Something to add to the list of features for Mach4?

Ideas would be appreciated.  I still need to find the cause of my hang. 


-Freeman

I use this to help me

http://www.machsupport.com/forum/index.php/topic,27162.msg193756.html#msg193756
 
maybe you can put the function at the first of the load script then use the code messages() in several locations in the load script so as it loads it runs the function and checks for new errors. If there are errors they get written to the file. so you can see what they were.

Thanks Craig that's helping.

One idea I had, if it doesn't already exist, is a command line option to come up in GUI edit mode.  That would allow the startup process to be avoided and have the user to be in the right place to do something about fixing it.

UPDATE - Uhm guess what?  There is an option to come up in edit mode, -e


-Freeman