| || |
root cause QA on Linux
To evaluate Linux compatibility on a specific hardware vendor's products, I've got to know that I shall take a series of test cases to do functional/press testing, thus make bugs happen.
But the question resides, how do I root cause these bugs according to the logs/dump files or associated symbols?
I've recognized that gdb's stack backtrace may be helpful, but I believe there must be some other methods to achieve it.
Anybody can help?