diff options
author | Thomas Schwinge <tschwinge@gnu.org> | 2008-03-24 18:29:41 +0100 |
---|---|---|
committer | Thomas Schwinge <tschwinge@gnu.org> | 2008-03-24 18:29:41 +0100 |
commit | 34f1fd3866c8e3f53d9a25bbae30426e8224a7b3 (patch) | |
tree | 1dfdf628989d853cd1d290e41fc54ffcb069e932 | |
parent | 5484f279ab10a68fff2fff8ceae86a11a80d5d96 (diff) |
hurd/running/debian/faq/debugging_inside_glibc: No esacping needed here for underscores.
-rw-r--r-- | hurd/running/debian/faq/debugging_inside_glibc.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/hurd/running/debian/faq/debugging_inside_glibc.mdwn b/hurd/running/debian/faq/debugging_inside_glibc.mdwn index 997bfadb..d28eccd7 100644 --- a/hurd/running/debian/faq/debugging_inside_glibc.mdwn +++ b/hurd/running/debian/faq/debugging_inside_glibc.mdwn @@ -12,8 +12,8 @@ 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 +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 |