From c355b6162685f828fb21fbe61bf8d74ac4effbce Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Mon, 3 Dec 2007 15:26:21 +0100 Subject: hurd/running/debian/faq/debugging_inside_glibc: Split out. Written by Michael Banck. --- hurd/running/debian/faq.mdwn | 14 -------------- 1 file changed, 14 deletions(-) (limited to 'hurd/running/debian/faq.mdwn') diff --git a/hurd/running/debian/faq.mdwn b/hurd/running/debian/faq.mdwn index 133667ca..bfd73dac 100644 --- a/hurd/running/debian/faq.mdwn +++ b/hurd/running/debian/faq.mdwn @@ -27,20 +27,6 @@ the respective Debian packages, or directly at # Porting Packages -# 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. - - # Debugging Translators In order to [[debug|debugging]] translators and being able to step into glibc -- cgit v1.2.3