Package: libc6-dbg Version: 2.3.6.ds1-8 Severity: normal
Edited highlights of a conversation on IRC with Daniel Jacobowitz (drow): <Igloo> I have the impression that I should be able to use gdb to step into libc functions if I set LD_LIBRARY_PATH to /usr/lib/debug, but it doesn't seem to work (for vfprintf, for example) (on amd64) <drow> it appears to be lacking line number info. <drow> probably it's built with -g1... I remember a couple platforms did that to work around old gcc bugs <drow> "vfprintf" itself is not interesting, because it's an alias, not a real function; if you step into it, you'll end up in _IO_vfprintf. <drow> yep, that's what happened. poke debian-glibc or file a bug report about that. <Igloo> Thanks for looking into it - is it OK to copy/paste the above into the report? <drow> sure Thanks Ian -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.14-2-amd64-k8 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages libc6-dbg depends on: ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]