I have a visual foxpro 6 application which is hanging (100% CPU). Process explorer etc don't indicate any activity, so it is obviously in some kind of loop.
For a .net or C app I would take a dump of the process when it is hung, and identify which method is causing the problem. Can a similar technique be done using foxpro, or any advice on how to identify the method involved?
We have complete access to the sourcecode, and can rebuild it. But we are unable to recreate the problem at our facility - we only see this happen occasionally at a single customer.