I do not think that this directory is intended to be listed in /etc/ld.so.conf; among other things, that causes every program on the system to run using these alternate libraries, which is rarely (if ever) advisable. The best thing to do is usually to run the program being debugged with LD_LIBRARY_PATH set to include /usr/lib/debug.
I would be quite surprised if this were the only thing to break in this situation, as far as the packaging system is concerned. libc6-dbg's strict versioned dependency on libc6 probably prevents some of the obvious pitfalls, but more subtle ones like this are likely to exist elsewhere. Package dependencies for glibc are expressed in terms of the libc6 package, and they do not anticipate getting linked with a potentially different version of libc6 from /usr/lib/debug or elsewhere. The same would apply to having /usr/local/lib early in the search path and installing another glibc there. This bug does not, in my opinion, warrant Severity: critical, if it is a bug at all. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]