Confirmed users
35
edits
QA/Automation/Projects/WebRTC/Crashtest Guide: Difference between revisions
Jump to navigation
Jump to search
QA/Automation/Projects/WebRTC/Crashtest Guide (view source)
Revision as of 12:59, 13 December 2012
, 13 December 2012→Check the testcase in the debug
| Line 126: | Line 126: | ||
If you don't know your profile name, call ''./firefox'' with the ''-ProfileManager'' flag, to see the available profiles, i.e. ''./firefox -ProfileManager''. | If you don't know your profile name, call ''./firefox'' with the ''-ProfileManager'' flag, to see the available profiles, i.e. ''./firefox -ProfileManager''. | ||
|} | |} | ||
Once the browser becomes unresponsive or crashes, check the output in the gdb prompt and look for an exception. In our case, you would see something like this: | Once the browser becomes unresponsive or crashes, check the output in the gdb prompt and look for an exception. In our case, you would see something like this: | ||
Assertion failure: i < Length() (invalid array index), at ../../dist/include/nsTArray.h:538 | Assertion failure: i < Length() (invalid array index), at ../../dist/include/nsTArray.h:538 | ||
Program received signal SIGSEGV, Segmentation fault. | Program received signal SIGSEGV, Segmentation fault. | ||
[Switching to Thread 0x7fffc76fe700 (LWP 15827)] | [Switching to Thread 0x7fffc76fe700 (LWP 15827)] | ||