summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2007-03-10 17:17:00 +0000
committerThomas Schwinge <tschwinge@gnu.org>2007-03-10 17:17:00 +0000
commit1b3f7fb65af5af5834735f18a0a91249d9b7a4fa (patch)
tree3094c505692f7c017b42ea94e2c40f4edd6e0f97
parent6bcae74f9c4f6d9625b184c86fc0ed7304bc2e88 (diff)
none
-rw-r--r--Hurd/Debugging.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/Hurd/Debugging.mdwn b/Hurd/Debugging.mdwn
index 65ac4629..5e94f65d 100644
--- a/Hurd/Debugging.mdwn
+++ b/Hurd/Debugging.mdwn
@@ -6,6 +6,10 @@
<http://lists.gnu.org/archive/html/bug-hurd/2007-02/msg00039.html>
+### <a name="noninvasive_mode"> _noninvasive_ mode </a>
+
+This essentially means that the program continues running as usual, but you can use GDB to get back traces and print variables (and watch them change underneath you). This can be helpful when debugging system wide default servers that shall not be stopped while debugging.
+
----
## <a name="Debugging_glibc"> Debugging glibc </a>
@@ -17,3 +21,9 @@ See [[DebuggingGlibc]].
## <a name="Debugging_via_subhurds"> Debugging via subhurds </a>
See [[DebuggingViaSubhurds]].
+
+----
+
+## <a name="General_Notes"> General Notes </a>
+
+For debugging the system wide default servers (like the root file system server or the _exec_ server), it is recommendable to instead debug them in a sub-hurd or at least use the _noninvasive_ mode when attaching GDB to them.