Hi, > Now it gets weird: Upon receiving Wolframs email, I checked on another box > with Debian stable (No NIS, kernel 2.4.23) and libc6 2.2.5-11.5 and it does > not show the bug.
I think I've tracked this down, it happens with libnss-db, which in turn relies on libdb3, where there appears to be a leak in the __db_upgrade function. "real_name" isn't freed in case of opening error. I'll submit a patch for db3 soonish. Nothing to do with glibc though. Regards, Wolfram. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
