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 390 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
401 Run with `CHROME_IPC_LOGGING=1` eg. | 401 Run with `CHROME_IPC_LOGGING=1` eg. |
402 | 402 |
403 CHROME_IPC_LOGGING=1 out/Debug/chrome | 403 CHROME_IPC_LOGGING=1 out/Debug/chrome |
404 | 404 |
405 or within gdb: | 405 or within gdb: |
406 | 406 |
407 set environment CHROME_IPC_LOGGING 1 | 407 set environment CHROME_IPC_LOGGING 1 |
408 | 408 |
409 If some messages show as unknown, check if the list of IPC message headers in | 409 If some messages show as unknown, check if the list of IPC message headers in |
410 [chrome/common/logging_chrome.cc](/chrome/common/logging_chrome.cc) is | 410 [chrome/common/logging_chrome.cc](/chrome/common/logging_chrome.cc) is |
411 up-to-date. In case this file reference goes out of date, try looking for usage | 411 up to date. In case this file reference goes out of date, try looking for usage |
412 of macros like `IPC_MESSAGE_LOG_ENABLED` or `IPC_MESSAGE_MACROS_LOG_ENABLED`. | 412 of macros like `IPC_MESSAGE_LOG_ENABLED` or `IPC_MESSAGE_MACROS_LOG_ENABLED`. |
413 | 413 |
414 ## Using valgrind | 414 ## Using valgrind |
415 | 415 |
416 To run valgrind on the browser and renderer processes, with our suppression file | 416 To run valgrind on the browser and renderer processes, with our suppression file |
417 and flags: | 417 and flags: |
418 | 418 |
419 $ cd $CHROMIUM_ROOT/src | 419 $ cd $CHROMIUM_ROOT/src |
420 $ tools/valgrind/valgrind.sh out/Debug/chrome | 420 $ tools/valgrind/valgrind.sh out/Debug/chrome |
421 | 421 |
(...skipping 115 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 |