From 10a5ed091374ee5d6421e6c55afd86b13c0f52a3 Mon Sep 17 00:00:00 2001 From: Pino Toscano Date: Fri, 15 Mar 2013 16:37:56 +0100 Subject: Reorganize the Hurd FAQ in a single place move all the hurd faq pages to the top-level faq directory; the faq.mdwn index now uses two simples map of all the subpages (one for the debian items, and the other for the non-debian items) TODO: now some of the items would need better titles --- faq/debugging_inside_glibc.mdwn | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 faq/debugging_inside_glibc.mdwn (limited to 'faq/debugging_inside_glibc.mdwn') diff --git a/faq/debugging_inside_glibc.mdwn b/faq/debugging_inside_glibc.mdwn new file mode 100644 index 00000000..91b71d64 --- /dev/null +++ b/faq/debugging_inside_glibc.mdwn @@ -0,0 +1,19 @@ +[[!meta copyright="Copyright © 2007, 2008, 2009 Free Software Foundation, +Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="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]]."]]"""]] + +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 +the frame unwind information used for backtracing. If you want to step into +glibc while debugging, you need to add `LD_LIBRARY_PATH=/usr/lib/debug` to +debugged program's environment (`set env VAR value` from the GDB command line). +If that still does not work, try `LD_PRELOAD=/usr/lib/debug/libc.so.0.3` +instead. -- cgit v1.2.3