diff options
Diffstat (limited to 'hurd/running')
| -rw-r--r-- | hurd/running/debian/faq/debugging_inside_glibc.mdwn | 15 |
1 files changed, 7 insertions, 8 deletions
diff --git a/hurd/running/debian/faq/debugging_inside_glibc.mdwn b/hurd/running/debian/faq/debugging_inside_glibc.mdwn index d28eccd7..375f042e 100644 --- a/hurd/running/debian/faq/debugging_inside_glibc.mdwn +++ b/hurd/running/debian/faq/debugging_inside_glibc.mdwn @@ -1,4 +1,5 @@ -[[meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] +[[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 @@ -11,10 +12,8 @@ is included in the section entitled 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. +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. |