| || |
Linux QA Root Cause Tools
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?
Re: Linux QA Root Cause Tools
It sounds like there are many ways to accomplish what you seek....
a couple ideas:
1) use err_rpt
2) Use an interactive debugger in the development environment.
I think it might be helpful to add more details to what you are trying to accomplish specifically regarding compatibility. Is it necessary that you determine the root cause, or simply develop and run tests that demonstrate compatibility?