Question: Are there any ways of logging or determining where deadlocks occur in the application provided to the client (perhaps by including some flags during the build process)?
Background: Usually, when I test the code and a deadlock occurs, I start in Visual Studio, so I can delete all debugs and find which thread is waiting and where, and I immediately know what the problem is. However, there is a certain problem due to which the application very rarely freezes (it was not detected in unit tests or integration tests). This happens on the client machine, where it runs the executable binary. I am interested to know if there are any features that I can enable that can help report these issues, since it is hard to say that this could be a problem without a debugger.
source
share