summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2025-02-02 11:29:31 +0100
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2025-02-02 11:29:31 +0100
commita4a250254a221887870dfd908496a037d2b4d2d1 (patch)
tree02b7d19271c8f968022cecbfa28123ed003c0c9c
parentc1fb288f792e5e292f3e9ad89fecc4a5837818b7 (diff)
There is no need to add LD_something nowadays
-rw-r--r--faq/debugging_inside_glibc.mdwn8
1 files changed, 2 insertions, 6 deletions
diff --git a/faq/debugging_inside_glibc.mdwn b/faq/debugging_inside_glibc.mdwn
index 2a75a1a7..cda43008 100644
--- a/faq/debugging_inside_glibc.mdwn
+++ b/faq/debugging_inside_glibc.mdwn
@@ -13,9 +13,5 @@ License|/fdl]]."]]"""]]
In Debian, 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.
+symbols by default (`/usr/lib/debug/.build-id`), Debian's `libc0.3-dbg` stores only
+the frame unwind information used for backtracing.