| Index: docs/linux_profiling.md
|
| diff --git a/docs/linux_profiling.md b/docs/linux_profiling.md
|
| index b1f874fa0fad56470e12d6d87a0e9fff5e3b9a81..4d9ce0f7764efa36910b308cbd82c00da96991e3 100644
|
| --- a/docs/linux_profiling.md
|
| +++ b/docs/linux_profiling.md
|
| @@ -164,7 +164,7 @@ http://google-perftools.googlecode.com/svn/trunk/doc/heapprofile.html.
|
| ### Massif
|
|
|
| [Massif](http://valgrind.org/docs/manual/mc-manual.html) is a
|
| -[Valgrind](http://www.chromium.org/developers/how-tos/using-valgrind)-based heap
|
| +[Valgrind](https://www.chromium.org/developers/how-tos/using-valgrind)-based heap
|
| profiler. It is much slower than the heap profiler from google-perftools, but it
|
| may have some advantages. (In particular, it handles the multi-process
|
| executables well).
|
| @@ -173,7 +173,7 @@ First, you will need to build massif from valgrind-variant project yourself,
|
| it's [easy](http://code.google.com/p/valgrind-variant/wiki/HowTo).
|
|
|
| Then, make sure your Chromium is built using the
|
| -[valgrind instructions](http://www.chromium.org/developers/how-tos/using-valgrind).
|
| +[valgrind instructions](https://www.chromium.org/developers/how-tos/using-valgrind).
|
| Now, you can run massif like this:
|
|
|
| ```
|
|
|