Wireshark may also be useful if the application appears to be hanging as a result of network activity. Maybe a few dumps using procdump when it has hung would also be good. Run Windows Performance Analyzer (Part of the SDK) to capture a ETL trace of the issue.Ĥ. Run Process Monitor of course but also add profiling events every 100 ms.ģ. Hopefully this will give you thread IDs and possibly PIDs if needed in the logs of the application assuming itĢ. You might need to consult with Support of the application in question. Enable as much trace logging of the application in question. ![]() I would suggest the following logs should cover everything:ġ. You may need more than just Process Monitor unless you have a really good understanding of the application in question.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |