diff options
| author | Thomas Schwinge <tschwinge@gnu.org> | 2007-09-05 15:33:28 +0200 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@gnu.org> | 2007-09-05 15:33:28 +0200 |
| commit | a5804a989267906cf4c61278af8207a4947a1653 (patch) | |
| tree | e6b914b75f1ee84756282436b8f7f7556e497d07 /hurd/neighborhurd.mdwn | |
| parent | b0b774a3e4d32e9dfb0e1c6287d0d5ff61500e91 (diff) | |
Rearrange some pages about debugging and neighborhurds and subhurds.
Diffstat (limited to 'hurd/neighborhurd.mdwn')
| -rw-r--r-- | hurd/neighborhurd.mdwn | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/hurd/neighborhurd.mdwn b/hurd/neighborhurd.mdwn index b4d25586..76ae20d1 100644 --- a/hurd/neighborhurd.mdwn +++ b/hurd/neighborhurd.mdwn @@ -27,12 +27,13 @@ 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]]) +([[subhurd]]) Sub-hurds are extremely useful for debugging core servers as it is possible to attach to them with gdb -from the parent ([[DebuggingViaSubhurds]]. This avoids +from the parent ([[debugging_via_neighborhurds|debugging/neighborhurd]]). +This avoids deadlock, e.g., when the instance of gdb stops the server but requires its use. -(Note: it is possible to use [[NonInvasiveDebugging]], +(Note: it is possible to use [[noninvasivedebugging]], but this is less flexible.) |