Originally Posted by anshuman84
Let me get clarity about your issue. If you are getting the issue after running the application then you can use following tools >>>>>>>
2>Valgrind (mainly for memory leak issue as I saw you CPU utilization shooting to 100%)
3>trace (To trace the system calls)
Firstly, support what anshuman84 said above.
Then, I think, the kernel debugger is necessary, such as KGDB (also need GDB in user mode on remote machine) or KDB (can debug in one machine).
KGDB is integrated into kernel in later version (but maybe not in 2.6.27), and KDB is later than KGDB for being integrated into kernel.
And by the way (maybe not quite relative with this issue)
Reading source code and programming carefully (especially for the relative changes) is still a way for solving this issue, it is the sugestion of Linus Torvalds.
Linus does not suggest using debugger: reading source code and carefully programming are much important than debugging (it is truly reasonable)