aboutsummaryrefslogtreecommitdiff
path: root/doc/stdenv.xml
diff options
context:
space:
mode:
authordeliciouslytyped <47436522+deliciouslytyped@users.noreply.github.com>2019-03-15 19:33:21 +0100
committerGitHub <noreply@github.com>2019-03-15 19:33:21 +0100
commit01e34d6b60e1b34b64398578c7bad72a2ca68132 (patch)
tree59dd610f157c160c15f8fcc146e77220891b3d4b /doc/stdenv.xml
parentfc32780cdfcdc05d20877d6c7c346f773a6fcb80 (diff)
Add word `debug(ging)` to breakpointHook description for discoverability
Diffstat (limited to 'doc/stdenv.xml')
-rw-r--r--doc/stdenv.xml3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/stdenv.xml b/doc/stdenv.xml
index 68a3282d7d6..a3990dec052 100644
--- a/doc/stdenv.xml
+++ b/doc/stdenv.xml
@@ -2633,7 +2633,8 @@ addEnvHooks "$hostOffset" myBashFunction
happens. It prevents nix from cleaning up the build environment
immediately and allows the user to attach to a build environment using
the <command>cntr</command> command. Upon build error it will print
- instructions on how to use <command>cntr</command>. Installing cntr and
+ instructions on how to use <command>cntr</command>, which can be used
+ to enter the environment for debugging. Installing cntr and
running the command will provide shell access to the build sandbox of
failed build. At <filename>/var/lib/cntr</filename> the sandboxed
filesystem is mounted. All commands and files of the system are still