summaryrefslogtreecommitdiff
path: root/faq/debugging_inside_glibc.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'faq/debugging_inside_glibc.mdwn')
-rw-r--r--faq/debugging_inside_glibc.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/faq/debugging_inside_glibc.mdwn b/faq/debugging_inside_glibc.mdwn
index cda43008..f3240c15 100644
--- a/faq/debugging_inside_glibc.mdwn
+++ b/faq/debugging_inside_glibc.mdwn
@@ -15,3 +15,5 @@ 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/.build-id`), Debian's `libc0.3-dbg` stores only
the frame unwind information used for backtracing.
+
+You also need to download the source code with `apt source glibc` and `cd` into it for `gdb` to be able to find and show it.