summaryrefslogtreecommitdiff
path: root/Hurd/NeighborHurd.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'Hurd/NeighborHurd.mdwn')
-rw-r--r--Hurd/NeighborHurd.mdwn9
1 files changed, 5 insertions, 4 deletions
diff --git a/Hurd/NeighborHurd.mdwn b/Hurd/NeighborHurd.mdwn
index ed76c4e1..89d7be02 100644
--- a/Hurd/NeighborHurd.mdwn
+++ b/Hurd/NeighborHurd.mdwn
@@ -10,11 +10,12 @@ When extra hardware is not available, it is possible to
use a sub-hurd. A sub-Hurd is like a neighbor Hurd,
however, makes use of some resources provided by another
Hurd. For instance, backing store and the console.
+([[SubhurdHowto]])
Sub-hurds are extremely useful for debugging core
servers as it is possible to attach to them with gdb
-from the parent. This avoids deadlock, e.g., when the
-instance of gdb stops the server but requires its use.
+from the parent ([[DebuggingViaSubhurds]]. This avoids
+deadlock, e.g., when the instance of gdb stops the
+server but requires its use.
(Note: it is possible to use [[NonInvasiveDebugging]],
-but this is less flexible.) A [tutorial](http://www.gnu.org/software/hurd/howto/subhurd.html)
-on setting up sub-hurds is available.
+but this is less flexible.)