Confirmed users
35
edits
QA/Automation/Projects/WebRTC/Crashtest Guide: Difference between revisions
QA/Automation/Projects/WebRTC/Crashtest Guide (view source)
Revision as of 13:26, 13 December 2012
, 13 December 2012→Check the testcase in the debug
| Line 109: | Line 109: | ||
{| border="1" cellpadding="5" | {| border="1" cellpadding="5" | ||
|'''SIDE NOTE:'''<br> | |'''SIDE NOTE:'''<br> | ||
Please make sure that | Please make sure that <tt>media.navigator.enabled</tt> and <tt>media.peerconnection.enabled</tt> in <tt>about:config</tt> is set to '''<tt>true</tt>''' before testing for the crash. If these are not enabled, nothing will happen. | ||
|} | |} | ||
<br> | <br> | ||
If this, however, fails the next option is to start firefox using gdb (for more information, please consult the following webpage: https://developer.mozilla.org/en-US/docs/Debugging_Mozilla_with_gdb ). | If this, however, fails the next option is to start firefox using <tt>gdb</tt> (for more information, please consult the following webpage: https://developer.mozilla.org/en-US/docs/Debugging_Mozilla_with_gdb ). | ||
Therefore from the command line call: | Therefore from the command line call: | ||
| Line 128: | Line 128: | ||
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 <tt>gdb</tt> 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 | ||
| Line 137: | Line 137: | ||
538 MOZ_ASSERT(i < Length(), "invalid array index"); | 538 MOZ_ASSERT(i < Length(), "invalid array index"); | ||
At this point, the gdb prompt should reappear. Now type | At this point, the <tt>gdb</tt> prompt should reappear. Now type | ||
bt | bt | ||