From f8735152c50e3e7b1315ea8ac38639062c0a0742 Mon Sep 17 00:00:00 2001 From: GNU Hurd wiki engine Date: Wed, 22 Aug 2007 17:09:40 +0000 Subject: web commit by NealWalfield: Add link to [[SubhurdHowto]] and [[DebuggingViaSubhurds]]. Remove link to Roland's Sub-Hurd text. --- Hurd/NeighborHurd.mdwn | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'Hurd') 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.) -- cgit v1.2.3