I have a project in which I have to fix this program, which tends to crash very non-deterministically. This piece of software performs many calculations and database queries and can have a very high load, which means many clients.
This is a very important component, and nothing works without it. He must perform and be able to work without user interaction for a long time.
This is actually a native C ++ / ATL project with COM for communication between its two executable files.
I spent a lot of time studying the code and looking for obvious code flaws, such as not blocking common variables (obvious), exception handlers that do nothing with exception, return false ', even if it could be a critical exception.
But I wanted to know if anyone had any advice on solving such a project, when many people really tried to fix the problem and couldn’t, and now you have taken the challenge and do not want to fail.
I am ready to go far to fix this, but do I need some guidance on how to do it right?
My idea is to first set up a test environment and hope to collect as much information as possible about the failures that occur, and then find through the log, stack trace, etc. failure points. This may or may not be a good way to debug such a project.
?