hurd/running/debian/faq/debugging_inside_glibc: Split out. Written by Michael Banck.

1 files changed, 20 insertions, 0 deletions

diff --git a/hurd/running/debian/faq/debugging_inside_glibc.mdwn b/hurd/running/debian/faq/debugging_inside_glibc.mdwn
new file mode 100644
index 00000000..85b58500
--- /dev/null
+++ b/hurd/running/debian/faq/debugging_inside_glibc.mdwn
@@ -0,0 +1,20 @@
+[[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]]."]]
+
+# Debugging inside glibc
+
+To get [[debugging]] information for glibc, you need to install the
+`libc0.3-dbg` package.  At the place [[debugging/GDB]] looks for debugging
+symbols by default (`/usr/lib/debug/lib/`), Debian's `libc0.3-dbg` stores only
+frame unwind information.  If you want to step into glibc while debugging, you
+need to add `LD\_LIBRARY\_PATH=/usr/lib/debug` to GDB's environment.  If that
+still does not work, try `LD\_PRELOAD=/usr/lib/debug/libc.so.0.3` instead.  You
+can add to GDB's environment via `set env FOO bar` from the GDB command line.
+
+It seems that this is no longer needed with the Debian glibc 2.5 packages, but
+I may as well be wrong.  Have to check that again.