diff options
Diffstat (limited to 'faq')
| -rw-r--r-- | faq/debugging_inside_glibc.mdwn | 10 | ||||
| -rw-r--r-- | faq/foo_max.mdwn | 2 |
2 files changed, 5 insertions, 7 deletions
diff --git a/faq/debugging_inside_glibc.mdwn b/faq/debugging_inside_glibc.mdwn index 2a75a1a7..8577dce3 100644 --- a/faq/debugging_inside_glibc.mdwn +++ b/faq/debugging_inside_glibc.mdwn @@ -13,9 +13,7 @@ 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. + +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, or use `set directories` inside gdb, or put it in your `.gdbinit` diff --git a/faq/foo_max.mdwn b/faq/foo_max.mdwn index 14015b9b..5f736680 100644 --- a/faq/foo_max.mdwn +++ b/faq/foo_max.mdwn @@ -39,7 +39,7 @@ since Posix 2008 `realpath(path, NULL)` and `getcwd(NULL, 0)` allocate the path dynamically. In general, using `FOO_MAX` in source code (with a large value) leads to code -that is not acually checking against overflows. `PATH_MAX` being 4096 is +that is not actually checking against overflows. `PATH_MAX` being 4096 is actually "wrong" on Linux: $ printf '#include <limits.h>\nPATH_MAX' | cpp -P |