Is it feasible to build an intelligent debugger to reduce debugging time?
We have a pretty vast and complex C++ code base developed for over a decade. Sometimes, when some issues are reported, we spend a lot of time debugging the issues eventually landing on some common area. The problem is particularly acute when new members join the team and has to spend considerable time debugging issues. I was thinking of developing some kind of intelligent debugger, something which can give some hints where to debug based on the nature of the problem, thus reducing turnaround time for bug fixing. I know it would be complicated, so just wondering if it is worth the effort. Has anybody worked on something similar and has some prior experience?
2 comments
"something which can give some hints where to debug based on the nature of the problem"
That could be something as simple as keeping those hints on a wiki. Why does it need to be integrated into the debugger?
That could be something as simple as keeping those hints on a wiki. Why does it need to be integrated into the debugger?
I want it learn and grow. Most developers won't be too interested in maintaining a wiki.