Tracking application crashes in 'C'
-
I am working on a database application, developed in 'C' programming language, which talks to database through the odbc drivers. What is the best way to track/troubleshoot the 'crash' errors like NULL pointers, memory crashes, etc? As the application is a huge code base, I am looking for one smart way to track the application crashes. Please suggest, if any?
-
I am working on a database application, developed in 'C' programming language, which talks to database through the odbc drivers. What is the best way to track/troubleshoot the 'crash' errors like NULL pointers, memory crashes, etc? As the application is a huge code base, I am looking for one smart way to track the application crashes. Please suggest, if any?
If you are not already using it, then the best first step is to use your debugger. You cannot do any advanced debugging without a debugger.
Cédric Moonen Software developer
Charting control [v3.0] OpenGL game tutorial in C++ -
I am working on a database application, developed in 'C' programming language, which talks to database through the odbc drivers. What is the best way to track/troubleshoot the 'crash' errors like NULL pointers, memory crashes, etc? As the application is a huge code base, I am looking for one smart way to track the application crashes. Please suggest, if any?
coder21k wrote:
What is the best way to track/troubleshoot the 'crash' errors like NULL pointers, memory crashes, etc? As the application is a huge code base, I am looking for one smart way to track the application crashes.
Write a crash report to identify application version, environment, registers, calling stack etc. Then assign each maintainer time to investigate and fix crashes, for a huge code base you probably have multiple teams/maintainers. If you have a ticket systems for defects the teams can create individual bug tickets after investigation and narrowing down the cause of a crash, marked as important. Application crashes are not only annoying for end users, they should be handled with high priority because they could be a sign for quality/security/development weaknesses. As an alternative you could add stress and penetration tests to your test strategy. Hope it helps :) /M