OLD | NEW |
1 # Tips for debugging on Linux | 1 # Tips for debugging on Linux |
2 | 2 |
3 This page is for Chromium-specific debugging tips; learning how to run gdb is | 3 This page is for Chromium-specific debugging tips; learning how to run gdb is |
4 out of scope. | 4 out of scope. |
5 | 5 |
6 [TOC] | 6 [TOC] |
7 | 7 |
8 ## Symbolized stack trace | 8 ## Symbolized stack trace |
9 | 9 |
10 The sandbox can interfere with the internal symbolizer. Use `--no-sandbox` (but | 10 The sandbox can interfere with the internal symbolizer. Use `--no-sandbox` (but |
(...skipping 346 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
357 Run your tests with graphics output redirected to that display: | 357 Run your tests with graphics output redirected to that display: |
358 | 358 |
359 DISPLAY=:6.0 out/Debug/browser_tests --gtest_filter="MyBrowserTest.MyActivat
eWindowTest" | 359 DISPLAY=:6.0 out/Debug/browser_tests --gtest_filter="MyBrowserTest.MyActivat
eWindowTest" |
360 | 360 |
361 You can look at a snapshot of the output by: | 361 You can look at a snapshot of the output by: |
362 | 362 |
363 xwd -display :6.0 -root | xwud | 363 xwd -display :6.0 -root | xwud |
364 | 364 |
365 Alternatively, you can use testing/xvfb.py to set up your environment for you: | 365 Alternatively, you can use testing/xvfb.py to set up your environment for you: |
366 | 366 |
367 testing/xvfb.py out/Debug out/Debug/browser_tests \ | 367 testing/xvfb.py out/Debug/browser_tests \ |
368 --gtest_filter="MyBrowserTest.MyActivateWindowTest" | 368 --gtest_filter="MyBrowserTest.MyActivateWindowTest" |
369 | 369 |
370 ### BROWSER_WRAPPER | 370 ### BROWSER_WRAPPER |
371 | 371 |
372 You can also get the browser under a debugger by setting the `BROWSER_WRAPPER` | 372 You can also get the browser under a debugger by setting the `BROWSER_WRAPPER` |
373 environment variable. (You can use this for `browser_tests` too, but see above | 373 environment variable. (You can use this for `browser_tests` too, but see above |
374 for discussion of a simpler way.) | 374 for discussion of a simpler way.) |
375 | 375 |
376 BROWSER_WRAPPER='xterm -e gdb --args' out/Debug/browser_tests | 376 BROWSER_WRAPPER='xterm -e gdb --args' out/Debug/browser_tests |
377 | 377 |
(...skipping 159 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
537 [Running layout tests on Linux](layout_tests_linux.md) page. | 537 [Running layout tests on Linux](layout_tests_linux.md) page. |
538 | 538 |
539 If you need to test something with hardware accelerated compositing | 539 If you need to test something with hardware accelerated compositing |
540 (e.g., compiz), you can use `Xgl` (`sudo apt-get install xserver-xgl`). E.g.: | 540 (e.g., compiz), you can use `Xgl` (`sudo apt-get install xserver-xgl`). E.g.: |
541 | 541 |
542 Xgl :1 -ac -accel glx:pbuffer -accel xv:pbuffer -screen 1024x768 | 542 Xgl :1 -ac -accel glx:pbuffer -accel xv:pbuffer -screen 1024x768 |
543 | 543 |
544 ## Mozilla Tips | 544 ## Mozilla Tips |
545 | 545 |
546 https://developer.mozilla.org/en/Debugging_Mozilla_on_Linux_FAQ | 546 https://developer.mozilla.org/en/Debugging_Mozilla_on_Linux_FAQ |
OLD | NEW |