diff options
| -rw-r--r-- | Hurd/Debugging.mdwn | 34 |
1 files changed, 7 insertions, 27 deletions
diff --git a/Hurd/Debugging.mdwn b/Hurd/Debugging.mdwn index 5e94f65d..8943c4e9 100644 --- a/Hurd/Debugging.mdwn +++ b/Hurd/Debugging.mdwn @@ -1,29 +1,9 @@ -## <a name="GDB"> </a> GDB +* [[DebuggingGlibc]] +* [[DebuggingViaSubhurds]] - To debug system servers -<http://sourceware.org/gdb/> +# GDB -[General GDB documentation](http://sourceware.org/gdb/documentation/), including the [special Hurdy bits](http://sourceware.org/gdb/current/onlinedocs/gdb_19.html#Hurd%20Native). - -<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> - -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. +* [Manual](http://sourceware.org/gdb/documentation/) +* [Hurd Specific](http://sourceware.org/gdb/current/onlinedocs/gdb_19.html#Hurd%20Native). +* [[NonInvasiveDebugging]] - Avoiding Deadload +* [When disassble doesn't work](http://lists.gnu.org/archive/html/bug-hurd/2007-02/msg00039.html) |