docs/linux_debugging.md - Issue 2545363002: Use HTTPS links for Google domains in docs

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: docs/linux_debugging.md

Issue 2545363002: Use HTTPS links for Google domains in docs (Closed)

Patch Set: Modify two more files in subdirectories Created 4 years ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Index: docs/linux_debugging.md

diff --git a/docs/linux_debugging.md b/docs/linux_debugging.md

index 3a67ce0429df5b0c1edbf32191b91d823956d17c..0049fd9dbf1eb7c89c9c9442dd8ded2cb659305f 100644

--- a/docs/linux_debugging.md

+++ b/docs/linux_debugging.md

@@ -80,7 +80,7 @@ which is rather annoying.

You can also use `--renderer-startup-dialog` and attach to the process in order

to debug the renderer code. Go to

-http://www.chromium.org/blink/getting-started-with-blink-debugging for more

+https://www.chromium.org/blink/getting-started-with-blink-debugging for more

information on how this can be done.

#### Choosing which renderers to debug

@@ -196,7 +196,7 @@ just run gdb on the main process.

Currently, the `--disable-gpu` flag is also required, as there are known crashes

that occur under TextureImageTransportSurface without it. The crash described in

-http://crbug.com/361689 can also sometimes occur, but that crash can be

+https://crbug.com/361689 can also sometimes occur, but that crash can be

continued from without harm.

Note that for technical reasons plugins cannot be in-process, so

@@ -394,7 +394,7 @@ Default log level hides `LOG(INFO)`. Run with `--log-level=0` and

`--enable-logging=stderr` flags.

Newer versions of Chromium with VLOG may need --v=1 too. For more VLOG tips, see

-[the chromium-dev thread](http://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/dcd0cd7752b35de6?pli=1).

+[the chromium-dev thread](https://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/dcd0cd7752b35de6?pli=1).

### Seeing IPC debug messages

@@ -485,7 +485,7 @@ this, run via `Xephyr`. Instructions for how to use `Xephyr` are on the

### Isolating Regressions

Old builds are archived here:

-http://build.chromium.org/buildbot/snapshots/chromium-rel-linux/

+https://build.chromium.org/buildbot/snapshots/chromium-rel-linux/

(TODO: does not exist).

`tools/bisect-builds.py` in the tree automates bisecting through the archived

« no previous file with comments | « docs/linux_chromium_arm.md ('k') | docs/linux_development.md » ('j') | no next file with comments »