diff options
| author |  Janak Ramakrishnan <janakr@google.com> | 2016-01-04 23:02:11 +0000 |
|---|---|---|
| committer |  Philipp Wollermann <philwo@google.com> | 2016-01-07 13:41:50 +0000 |
| commit | e7194d9758a740272dd0cb8ea456c996c7503485 (patch) | |
| tree | 68252d1c74fb80a9e040bad63a6d717f0dae72a7 /site | |
| parent | 98ed561455740756899f86b5e525d2d4d59781d2 (diff) | |
Document that ctrl-\ causes Bazel to dump its threads to its jvm.out file, to aid in diagnosing issue #748.
--
MOS_MIGRATED_REVID=111360258
Diffstat (limited to 'site')
| -rw-r--r-- | site/docs/bazel-user-manual.html | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/site/docs/bazel-user-manual.html b/site/docs/bazel-user-manual.html index 62261d6881..c72545eeb2 100644 --- a/site/docs/bazel-user-manual.html +++ b/site/docs/bazel-user-manual.html @@ -3752,3 +3752,13 @@ Start time: [time elapsed from the profiling session start] Duration: [tas </ul></li> </ul> +<p>If Bazel appears to be hung, you can hit <kbd>⟨Control⟩</kbd>-<kbd>\</kbd> or send Bazel + a <code>SIGINT</code> signal (<code>kill -3 $(bazel info server_pid)</code>) to get a + thread dump in the file <code>$(bazel info output_base)/server/jvm.out</code>. +</p> + +<p> + Since you may not be able to run <code>bazel info</code> if bazel is hung, the + <code>output_base</code> directory is usually the parent of the <code>bazel-base_workspace</code> + symlink in your workspace directory. +</p> |