Some bits about how to get a backtrace.

1 files changed, 27 insertions, 0 deletions

diff --git a/hurd/debugging/gdb/backtrace.mdwn b/hurd/debugging/gdb/backtrace.mdwn
new file mode 100644
index 00000000..62067392
--- /dev/null
+++ b/hurd/debugging/gdb/backtrace.mdwn
@@ -0,0 +1,27 @@
+[[meta copyright="Copyright © 2007 Free Software Foundation, Inc."]]
+[[meta license="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
+is included in the section entitled
+[[GNU_Free_Documentation_License|/fdl.txt]]."]]
+
+When someone asks you to supply a backtrace (from a [[segmentation_fault]], for
+example), here is roughly what you have to do.
+
+Run the faulting program like this:
+
+    $ gdb --args PROGRAM [ARGUMENTS]
+    [...]
+    (gdb) run
+    [...]
+    [Segmentation fault.]
+    (gdb) bt
+    [...]
+
+(!) This will only provide useful information if the executable (and additional
+libraries) contain debugging symbols, or those are available separartely.
+
+If you're one a [[Debian_GNU/Hurd_system|running/distrib/debian]], you'll have
+to have the *hurd-dbg* package installed for debugging Hurd stuff, and perhaps
+*libc0.3-dbg* as well if it's inside the glibc.